Earlier quoted context omitted.
> these roles are usually high stakes and the cost of a bad hire is too high Really? High stakes? This fucking site. Have you ever worked as a software developer at a corporation? Nothing about it is high stakes. You spend most of your time dealing with useless idiots who report to other useless idiots, who report to other useless idiots, about a useless product they think is a great idea that every non-idiot knows i…
High stakes means high investment. You can’t just hire a dev and have them running in a week, their bad work could cost the company multi-millions in obvious and non obvious ways and proper onboarding takes months at minimum. On the other hand, a cashier can be replaced in a week, and they don’t effect the entire future of the company as SOP.
That's such patently absurd bullshit. Google has a code review process. Almost any large tech company has this today. The review process is to ensure that it's a team effort when a major screw-up happens. You don't just let some new employee merge untested and unreviewed code.
You know who I always see harming the company with outages and downtime? Seniors and managers that cut corners. I've had managers before that put in place all these safe guards that go out the window the very second a deadline is threatened. They merge untested code. They route traffic haphazardly. They fuck around with DNS or user accounts on a whim. Because no one is there to tell them not to. They believe they are the exception. The rules are for the minions below them. If you're working late on a weekend cleaning up a huge mess, there is a good chance it's because some manager-turned-arsonist fucked around with the process. They cut corners on the planning, the implementation, or the roll-out.