3 ms·
It is your fault. If you introduce a bug and let's say in part due to insufficient documentation in the code, code reviews that didn't catch it, your change pa
by throwawaylinux 5y ago
It is your fault.
If you introduce a bug and let's say in part due to insufficient documentation in the code, code reviews that didn't catch it, your change passed all tests and you even made some new tests to exactly test corner cases of the change you were making, it ran fine in beta testing. Then it is still (in part) your fault!
Everybody makes mistakes, and systems should be resilient to mistakes. That doesn't mean nobody is at fault for anything. It means everybody has faults, and if somebody doesn't think they have any faults then why should they think they have anything to learn or improve?
Fault finding should be done. People who wrote the documentation should be given notice and opportunity to improve. People who reviewed the change should as well. And certainly the person who introduced the bug. If people can not cope with accepting the blame for a problem they had responsibility for introducing, they should not be in that line of work.