Re:Why Twitter didn’t go down: From a real Twitter SRE
by john_the_writer on Tuesday November 22, 2022 @05:35PM
(#33712528)
Agreed.. but lets say you fire 99% of your engineers, and declare a code freeze (because there's no-one left to write code)..
Then in theory.. if you own the hardware and you've locked down the libraries... That code could keep running for a long time. Agreed it's not a Palm app, but with everything locked down, I'd argue it's safe
But now I will agree third party stuff will change. Payment processors and such. Those don't happen fast though, and 100% not so fast that a company the size of twitter can't work out a sunsetting.
To the heat can break software if the server it's running on overheats. I have a feeling twitter's has a system in place to scale out the faulty server.
My point was, comparing code to a car is silly. A car needs maintenance. Code in code freeze does not.
Then in theory.. if you own the hardware and you've locked down the libraries... That code could keep running for a long time. Agreed it's not a Palm app, but with everything locked down, I'd argue it's safe
But now I will agree third party stuff will change. Payment processors and such. Those don't happen fast though, and 100% not so fast that a company the size of twitter can't work out a sunsetting.
To the heat can break software if the server it's running on overheats. I have a feeling twitter's has a system in place to scale out the faulty server.
My point was, comparing code to a car is silly. A car needs maintenance. Code in code freeze does not.