The solution to this problem is code review. Good developers do not want bad code in the codebase. If you give them authority to stop bad code getting in, it wo

The solution to this problem is code review. Good developers do not want bad code in the codebase. If you give them authority to stop bad code getting in, it won't. Unfortunately, 'negative work' developers are often perceived by the rest of the organisation to be doing good work. They can make quick changes and deliver results fast. It is almost impossible to measure the real impact a developer's changes has, but easy to measure how much they are doing week-by-week. Therefore, the only practical way to make the issue apparent is by stopping the bad code getting in. So when the developer says my work is "done", it sits in code review for another 2-3 works until it is "done done".