Who makes sure Google never goes down

SRE is a wild ride :)

I was a Google SRE for two years. Three months after joining I was about to go oncall for the first time and I was worried about "what happens if I get paged!"

The first day of my first shift, before lunch, I got paged twelve times. It was trial by fire. My teammates coined the term "Gabriel Shift" to describe an oncall shift when everything catches fire at the same time.

It was stressful, but I did miss the adrenaline when I moved to SWE. It's cliche, but it made me feel alive :)

To my former brothers in arms: THIS IS A PAGE FROM TELEBOT. TELEBOT TELEBOT TELEBOT.

Very informative video on SRE at Google: https://www.youtube.com/watch?v=H4vMcD7zKM0&list=PLIivdWyY5s...

Wow they're pimping this new book hard, aren't they?

Have to take issue with this reduction by the article's author:

> Don’t get IT people who specialize in running Internet services to run your Internet services. Have software coders run them instead.

The point is that one should consider the former to be a subset of the latter.

holy hell really pushing the new SRE book really hard

This article really ought to be titled "Who makes sure Google never goes down". It's pretty scant on actual details about SRE there.

Flagging because we don't need a second day of front page items being marketing posts for a book. Google is using it's press contacts to try and get this book on the bestseller list to make their company look good, we get it. An ad for a book isn't HN-worthy.