2 ms·
Not OP but I'll give my take because I mostly agree. Because Google lives in a world few of us do. I'm SRE/DevOps and our lives are nothing like Google SREs. We
by stackskipton 2y ago
Not OP but I'll give my take because I mostly agree. Because Google lives in a world few of us do. I'm SRE/DevOps and our lives are nothing like Google SREs. We have almost zero control over software that is chucked our way. Any attempt to try and control them fails with management telling us "Just fucking ship it". Finally, something I realized after working with various FAANG SRE types, they don't understand what bad development practices look like, they can't imagine it.
- VirusNewbie 2y agoBut then that's not SRE, that's just Ops, who is called SRE...
- stackskipton 2y agoBut we are labeled SREs, we follow some of SRE practices. No True Scotsman arguments are pointless.
- VirusNewbie 2y agoGoogle invented the term SRE. And by your own words… “our lives are nothing like Google SREs”. The whole point of google inventing a new title and team, from Ben Teynor’s mouth, was that ops should be superseded by a specialization of SWE called SRE. If your company doesn’t support that, it’s not SRE.