undefined | Better HN

0 pointsoblio2y ago0 comments

> Middle management finds a tactic that implements the friction strategy - small "random" breaks and persistent performance issues.

> An engineer would find the precise measure to implement - break the UA string sniffing targeting a specific browser.

You got the strategy right but the implementation is laughable, sorry :-)))

The implementation is: "We have a budget of N story points this sprint to resolve bugs, let's prioritize them. Let's prioritize by impacted audience size."

The audience size will make 99% of Firefox specific bugs be deprioritized out of the current sprint. And the next one. And the one after that.

And unless a senior engineer stands up to update the prioritization criteria, plausible deniability forever.

0 comments

close042y ago

The aim was to lay out at which level each stage happens. It's not middle management taking a random decision. The fish rots from the head but the tail certainly doesn't smell rosy either. Dieselgate was also just a random deprioritized code bug until it wasn't.

Repeated incompetence from one level is actual maliciousness from the level above, all the way to the top.

j / k navigate · click thread line to collapse