Hacker News new | past | comments | ask | show | jobs | submit login

The SRE book is a little more advertisement of Google's internal systems than real actionable advice outside of Google for SREs.

There is some generally useful stuff in there, but it probably fits in a few pages vs a full book.




Only a few paragraphs into the book:

> One continual challenge Google faces is hiring SREs: not only does SRE compete for the same candidates as the product development hiring pipeline, but the fact that we set the hiring bar so high in terms of both coding and system engineering skills means that our hiring pool is necessarily small.

I was thinking, ok so does this mean the book is completely useless for most companies in the world, since they don't have such standards for hiring people or run DevOps this way? How much of the rest of the book is still applicable?


Most SWEs are SREs, they just don't realize it. If you're on call, you're a SRE.


The second book is actually actionable, according to coauthors.


By second book, do you mean the SWE book? https://abseil.io/resources/swe-book

It was written by titans with the SWE ladder at Google, fairly disconnected from the SRE book.



This seems easier to digest, but it's a long way off from The Practice of System and Network Administration of yesterday.


It’s really an incredible marketing piece




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: