In IT development, there is a tendency to consider bugs as a great sin, and while bugs do degrade the quality of the service, it seems to be a matter of consideration whether the developer who created the bug should be blamed.
I have experience as both a developer and a development manager, and I am sharing the experiences I have gained through them.
In the development and operation of IT services, the occurrence of bugs certainly degrades the user's service experience. Then, should the developer who created the bug be blamed? It seems so at first glance, but it is not.
Previously, an acquaintance in a specific field talked about using the number of bugs as a performance management indicator for developers.
Thinking that bugs = bad, developers who create bugs = incompetent developers, or developers who are not helpful, can have a very negative impact on the development team.
If bugs lower your performance score, no one will try to develop excessively, and the schedule will also be very defensive. Because you have to avoid bugs. They will oppose unreasonable development and try to pass on unfamiliar development to others. The development team will take a very negative trend.
Especially in the case of startups, where there is a lack of skilled developers and limited time available, if you try to evaluate developers based on bugs, the phenomenon of avoiding development will become noticeable.
Bugs are more often caused by a lack of experience in the relevant domain or a lack of development experience than by development skills.
The frequency of bug occurrences is normal to decrease over time, and if the frequency of bug occurrences suddenly increases, it is recommended to discuss the allocation of development tasks or the lack of development time with the development team. What tasks are our developers focusing on now? Is the bug fix frequency increasing or decreasing?
