Our model has always been that the reviewer is responsible for protecting the repository. This led to one IC getting fired for “letting in” a catastrophic bug his teammate generated with Claude.
I’m sorry that you work at a company that thinks code reviews and tests guarantee bug-free code.
The primary function of code reviews is to increase visibility, and therefore maintainability. It keeps other members of the team in the loop about how codebase is changing and how it might affect their current or future work.
The primary function of tests is to catch regressions, not new bugs, and especially not new bugs related to use cases that weren’t even possible in previous versions
Yes, but the situation is getting strange.
Our model has always been that the reviewer is responsible for protecting the repository. This led to one IC getting fired for “letting in” a catastrophic bug his teammate generated with Claude.
I’m sorry that you work at a company that thinks code reviews and tests guarantee bug-free code.
The primary function of code reviews is to increase visibility, and therefore maintainability. It keeps other members of the team in the loop about how codebase is changing and how it might affect their current or future work.
The primary function of tests is to catch regressions, not new bugs, and especially not new bugs related to use cases that weren’t even possible in previous versions