Hacker News Reader

Comment by pyfon | Hacker News Reader

False dichotomy. "If you deploy this code as is to production there is a high risk of bug X which I think is unacceptable risk. We had a similar bug 3 months ago.". Click the request changes button. Simple.

If someone keeps making mistakes, talk to their manager maybe. .

View on HN

That problem is already caught, how do you make sure they know and understand that mistakes like that cause harm and it was a result of their negligent attitude? Fixing that mistake isn't the goal, making sure they exercise more care and understand the gravity of the situation is.

"making sure they exercise more care" is quite a vague concept. If things are important there will be checks and extra safety nets and people will learn over time. If the only thing stopping harm is people "caring more", then you have a ticking time bomb on your hands anyway. And yeah, you can just tell someone "this is very important and serious" to convey it's very important and serious. Adding asshole phrasing on top doesn't change much.

it doesn't work that way in reality. You can monitor/check for bugs you can anticipate, but some bugs fall through the cracks and you have RCE's and outages causing millions of dollars. There is a limit both in terms of imagination and available resources on what you can anticipate and prepare for. There will never be a world where humans won't have to catch corner cases and bugs that would cause severe harm.

I'm not saying the checks and safety nets have to be automatic. QA, reviews, design sessions exist for a reason.

Reply on news.ycombinator.com