3 ms·
That's not "become the joker;" that's facts. The SRE book was, literally, Googlers documenting how they did SRE at Google. The book (i.e. the first two chapters
by nunez 3y ago
That's not "become the joker;" that's facts. The SRE book was, literally, Googlers documenting how they did SRE at Google. The book (i.e. the first two chapters) got cargo-culted everywhere, everything else became footnotes. See also: The massive set difference of places that have something resembling SLOs and places that implement interrupts and fair compensation for on-call rotations.
- steveBK123 3y agoYes, exactly. I've seen small companies that are smaller than Google's SRE staff alone try to implement the concept. As it turns out if your entire tech org is 50~200 people, hiring 2 people to "do SRE" because the CTO read a book.. is not gonna do the trick. CTO gonna get pretty dashboard though!
- nunez 3y agoAh, yes, the SLO Dashboard™ that makes at least eight gagillion dollars for Datadog every year that looks super pretty for execs but is amazingly useless for SREs that actually need to fix shit at 0330. i.e. basically this: https://www.youtube.com/watch?v=VQPIdZvoV4g&pp=ygUadGhlIG1hY2hpbmUgdGhhdCBnb2VzIHBpbmc%3D https://www.youtube.com/watch?v=VQPIdZvoV4g&pp=ygUadGhlIG1hY...
- steveBK123 3y agoI assume it was on a Gartner Magic Quadrant