News for hackers. Stuff that matters.
Re:Google Cloud Networking reporting issues by dmlittle on Wednesday March 17, 2021 @02:30PM (#26495069)
No, it was SolarWinds that blamed the intern for their security issues.

In all seriousness... if a single employee can accidentally single-handedly screw things up you've got a process problem. There should be checks and balances to make sure that what you're trying to do make sense. These might be in the form of a code-review, automated validation, a staging environments, etc. Yes, these might be things that don't exist at a scrappy startup and that is fine as they'll get there eventually but for any large company not having good processes is reckless.

Re:Google Cloud Networking reporting issues by throwaway53453 on Wednesday March 17, 2021 @03:23PM (#26495734)
These issues happen despite all those things. You can bet that Google has that and more in place. Just like in aerospace engineering, things go wrong when dozens of failures happen across the critical path, not any individual piece.
Re:Google Cloud Networking reporting issues by dmlittle on Wednesday March 17, 2021 @03:30PM (#26495806)
Yes, and issues will always occur. What I was trying to point out that it's never an individual's fault alone. Sure someone might have tripped the final domino but they might not have had anything to do with everything else that happened. That's why blameless postmortems are a thing. Blameless (to me) doesn't mean that you don't name any person but rather that there's no blame assigned to anyone. I want to know what Person A did to cause the incident but there shouldn't be any retribution against Person A.