Comment by 542354234235

But you don’t know negligence is the reason. You are just assuming that you understand how the situation arose and what their internal state of mind was the led to it. But it could have ignorance, rather than “negligence”. They might not fully understand that specific code usage, in which case instruction and mentorship would be the remedy.

Second, do you have any evidence that calling someone negligent actually leads to better performance? Is that an established best practice for reducing errors or does that just satisfy your own feelings of annoyance or dissatisfaction?

Third, “this is negligent” is not constructive. Neither is "This is really bad, you messed up, this type of a mistake is unacceptable and horrific". These are not actionable nor are they specific. They are emotional. Feedback outlining (or directing them to resources) on how to do a proper code review to catch mistakes like this, is actionable and specific.

Finally, the swiss cheese method of safety is always better than the “just stop making mistakes” method. Aviation safety does not rely on pilots “just not making mistakes”. There are studies of procedures, warnings, training, etc. to reduce the likelihood of an arror and redundant systems to make errors survivable. And there are checklists, so many checklists. Have you instituted checklists for code writing and review before it comes to your level? If something is so critical, is it negligent to allow code to be written and submitted based on each persons individual, subjective idea on what is thorough and what is a negligent level of review?