When problems appear in an app or website, for some people the first move is to blame the developer(s). Sure, it’s true that the developers wrote the code. But the reality is that bugs are rarely the fault of any one person or group. There are many reasons why developers shouldn’t always be blamed for bugs. A developer’s build could have a bug for many different reasons, including:
- Vague or incomplete acceptance criteria
- A regression (when a fix or new feature causes problems with older code)
- Issues with specific devices or browsers based on new updates
- Rushed timelines in an Agile process
Between these explanations and the reasons below, it’s a good idea to think twice before defaulting blame to developers.
Why Developers Shouldn’t Always Be Blamed for Bugs
1. It’s counter-productive.
Adding extra pressure is only going to make bugs more likely, as insecurity and nervousness interfere with focus. Of course, having some level of accountability is usually helpful (and reasonable). But there’s a difference between asking someone why certain bugs made it through vs. interrogating them with negative assumptions. Continue reading →