It sounds more like your company has failed to implement robust processes to catch mistakes before they're big problems to me. No individual should have the power to destroy the company except maybe a CTO or a lead sysadmin. For everything else important there should be layers of security and QA checks, with automated sanity checks on config and data for really important stuff. If a new hire can deploy stuff without multiple people seeing it before it gets to production then everyone in the company is responsible for accepting a process that can lead to serious issues.
What makes you think those two fuck ups by the same person where the same kind of mistake, or even related?
That sort of bureaucratic process is horrible and annoying, but it's less horrible and annoying than everyone losing their jobs when the company fails.
We're very fortunate in tech that we can automate 99% of this stuff. Stopping someone pushing bad code that fails tests or hasn't been peer reviewed is a straightforward case of adding some deploy rules to a repo. It's much harder to fix processes where things are manual checklists people need to follow.
When you're scaling up, or when you're short on staff, and there are fires to be put out everywhere, you just don't have the capacity to design and test those perfect processes. Where are they supposed to come from?
> layers of security and QA checks, with automated sanity checks on config and data
Ha! I've never, ever seen any company which comes even close to that platonic ideal.
A lot of companies choose not to do process oriented work, and just wing it instead because they believe they can go faster. That's fine. It's a choice driven by resources.
What's not fine is complaining that someone you hire is "bad" because they get stuff wrong when you're forcing them to work without a process-based safety net. People will always make mistakes. If your belief is that everyone should be perfect because you've chosen the no-safety route then you don't get to complain when someone nearly sinks the company. Expecting people never to get things wrong is unreasonable, and it's the exact reason why we have processes to catch problems.
Well, you seem to believe there's such a thing as a perfect process. How is a non-perfect employee (or a group of non-perfect employees) supposed to come up with a perfect process?
> [...] because you've chosen the no-safety route [...]
Who said anything about no safety net? Maybe there was a process, or a safety net, but it wasn't perfect and didn't catch those mistakes?
Focusing on process and making the safest process will kill your team. Your best team members don't want to be hampered by a process that slows them down to protect them from their worst team members. The advantage you have as a startup is speed, don't throw it away so easily.