Earlier quoted context omitted.
This is factually not true. Developers can make big mistakes to bring entire companies down with them. Of course it depends on the definition of "mistake". However I can claim that a single defect caused by a developer can cost the company money and downtime, if nothing else a bad user experience. Managers don't generate defects. Developers do. Not to mention that a lot of the times it's much harder to reverse an eng…
You sound like someone who has never been a manager or has no idea what a manager does. Yes, you're right that defects are made by developers. But you'd be hard pressed to find an example of a software defect that destroyed a company. Even if you as a DevOps engineer cause your company to be down for a day, it probably would have little effect on your company's bottom line. I was in charge of Reliability for Netflix.…
> Creating entire new groups of engineers and then hiring them to solve specific problems of moving traffic between regions.
Albeit admirable, like heck yeah that was a great outcome, it's not a manager decision. Most likely it was a VP or Sr Director decision. Perhaps a manager brought it up as an idea. So if we are talking about Sr Director's+ then yes, their decisions can absolutely bring down a business. Granted I am not familiar with Netflix's org chart so perhaps it works differently, from some basic reading it looks like Netflix follows a decentralized command of sorts.
My beef with the original poster was the implication of risk. Both managers and devs have risk with their decisions. It's not just a manager thing. In the end, when Netflix went down where did the mistake come from? A manager or an architecture decision? Probably it was both.