Re:Why Twitter didn’t go down: From a real Twitter SRE
by grayfaced on Tuesday November 22, 2022 @12:22AM
(#33702317)
But real world conditions can force code changes. For example, a region abandons daylight savings time or a court order on copyright infringement. Someone unqualified working a system they are unfamiliar with could blow it up. Losing that knowledge of how the system works is a risk.
[ Parent
| on HN ]
Re:Why Twitter didn’t go down: From a real Twitter SRE
by threeseed on Tuesday November 22, 2022 @02:39AM
(#33703126)
> But real world conditions can force code changes
Security fixes.
Re:Why Twitter didn’t go down: From a real Twitter SRE
by orwin on Tuesday November 22, 2022 @03:48AM
(#33703544)
Wasn't last year where a bug in a Java well-used lib (and pretty easy to use) caused mayhem in every SRE/SEC services in every banks? It was a fun two weeks. I worked like 50 hours the first three days.
Re:Why Twitter didn’t go down: From a real Twitter SRE
by snovv_crash on Tuesday November 22, 2022 @08:19AM
(#33705415)
Log4j