Reddit reviews Web Operations: Keeping the Data on Time

> Google literally wrote the book on this stuff.

Well, they wrote the book on Site Reliability Engineering. People outside Google have been talking about this stuff for a lot longer, e.g. the Web Operations book.

All your points still stand, but there's a lot more industry consensus out there than just Google. Which is good, because the things Google does often only make sense if you're Google (or possibly Facebook).

This quote from the book "Web Operations" nails it:

>“Generation X (and even more so generation Y) are cultures of immediate gratification. I’ve worked with a staggering number of engineers that expect the “career path” to take them to the highest ranks of the engineering group inside 5 years just because they are smart. This is simply impossible in the staggering numbers I’ve witnessed. Not everyone can be senior. If, after five years, you are senior, are you at the peak of your game? After five more years will you not have accrued more invaluable experience? What then? “Super engineer”? Five more years? “Super-duper engineer.” I blame the youth of our discipline for this affliction. The truth is that there are very few engineers that have been in the field of web operations for fifteen years. Given the dynamics of our industry many elected to move on to managerial positions or risk an entrepreneurial run at things.”

I'm a Windows admin who wanted to learn more Linux. I asked a friend the same question as you recently. He recommended A Practical Guide to Commands, Editors and Shell Programming by Marc Sobell as well as Web Operations by John Allspaw and Continuous Delivery by Jez Humble. He recommended I start with Sobell's book before moving on to the others.

:/ I haven't had much time to actually read any of this, but I trust his advice.

Web Operations: Keeping the data on time gives perspective from several authors on different aspects of scalability, design, delivery, ect. Gives a good idea of the breadth of the DevOps world.