4 ms·
There's still good advice in the book, but be aware it was published in 2016, with folks likely having started writing it around 2014. Both Google and SRE/DevO
by rozenmd 3y ago
There's still good advice in the book, but be aware it was published in 2016, with folks likely having started writing it around 2014.
Both Google and SRE/DevOps have advanced greatly since then, and following the book blindly would be cargo culting.
Edit: apparently this is a controversial opinion?
- esafak 3y agoWhat contemporary book do you recommend?
- Rapzid 3y agoHow has it advanced greatly since then?
- lrem 3y agoMost of the tools I’ve been using when my colleagues were writing the book are either gone, or half-forgotten abandonware. The new tools were built for different processes, system layout and organisational structures.
- Rapzid 3y agoBook barely talks about tools. It wasn't about tools. The epiphany for many was the concept of an error budget and establishing SLOs. Then, basing investment in reliability on data. That's as applicable today as it was then.
- malwarebytess 3y agoSo, what exactly do you propose as an alternative?