Tackling the Endless Stream of Bugs
How poor management can become the root cause of persistent software bugs and what to do about it.
Surely, you’ve seen it more than once: you’re developing an application and you keep finding bugs. Or even worse, with each new feature, the number of bugs grows, or fixing one bug leads to the emergence of new ones. And we’re not just talking about minor issues, but catastrophic errors that prevent normal use of the application. The experience is disastrous, and nothing seemed to stop the progression. Despite trying various strategies, there seemed to be no remedy: more and more errors kept appearing. Stopping new features to fix bugs, prioritizing defects over features, assigning employees only to bug fixing, but nothing has effect. And eventually, the viability of the application, the programming team’s capability, and even the management get questioned. Don’t you feel like playing whack-a-mole with bugs? As soon as you fix one, another comes up? How can we stop it?
Usually, when an error is this catastrophic, the first point to examine without a doubt is management. One might think it’s about firing the bad programmers and hiring new ones, or replacing the architects, but that’s not the case.
The worst employees ever… or worst managers ever?
