> What do you mean? You think all coders are security engineers?
Now, imagine using that argument when a bridge falls down. "What do you mean? You think all the bridge builders were safety engineers? Bridge components rely on different dependencies, often dozens at the same time. You just need one point of failure and boom, it collapses. These are humans creating these bridges. I would say that SPECIALLY because of the size of these bridges, collapses are inevitable."
Comparing bridges to a streaming service is nonsensical, frankly.
People die when bridges collapse. People get mildly inconvenienced if twitch is slow or down.
Accordingly bridge construction takes security & safety much more seriously throughout the project. And it's orders of magnitude more expensive to build and check bridges for safety issues, etc.
But it's still true that each individual contractor in a bridge project is not a bridge integrity engineer. I was replying to GP who said
> What all these coders do all day?
Implying that all coders have to care about everything in their stack. Putting the blame of UX devs or data engineers for the platform to be offline doesn't make any sense. Even hiring more platform engineers doesn't necessarily fix this issue. Like when building a bridge, you avoid this problem with good architecture.
Now, imagine using that argument when a bridge falls down. "What do you mean? You think all the bridge builders were safety engineers? Bridge components rely on different dependencies, often dozens at the same time. You just need one point of failure and boom, it collapses. These are humans creating these bridges. I would say that SPECIALLY because of the size of these bridges, collapses are inevitable."