3 ms·

The article talks about services at Google being relatively stable and SREs there focusing on automating the instability away. A previous comment here also ment

The article talks about services at Google being relatively stable and SREs there focusing on automating the instability away. A previous comment here also mentions that. In my experience, I find that to be not really true and more of a marketing image. The stress that being a Google SRE poses on family and relationships is huge and the job really is just like DevOps at other large service-based companies. The amount of code you write is orders of magnitude less compared to a software engineer since there is significant tooling available(Google being a mature company). Most of the work done is just operating those tools. I had an SRE girlfriend who became an ex because of the stresses it placed on our relationship. Although I was the one who helped her land the job and was with her through previous hardships, there were just too many missed dates and too little respect for my time and other stress related issues that breaking up was the only way out for me to regain peace of mind. Maybe you need a certain sort of person to handle that kind of stress.

honkhonkpants 10y ago
Google is a big enough organization that experience varies. When I was an SRE I wrote C++ code pretty much all day every day, even while being oncall, with only the occasional intervention necessary on my part. Teams like you describe are considered to be in "operational overload" and are actively dismantled by senior leadership, with responsibility for the dodgy systems devolving on the people who wrote them in the first place.
- throw_away_981 10y ago
  "Teams like you describe are considered to be in "operational overload" and are actively dismantled by senior leadership.." -In theory, maybe... But with the expectation to stay in said team for atleast a year or two before switching teams and the associated difficulty in actually doing it, I think it is a pretty bad postion for said SREs to be in.

honkhonkpants 10y ago

Google is a big enough organization that experience varies. When I was an SRE I wrote C++ code pretty much all day every day, even while being oncall, with only the occasional intervention necessary on my part. Teams like you describe are considered to be in "operational overload" and are actively dismantled by senior leadership, with responsibility for the dodgy systems devolving on the people who wrote them in the first place.

throw_away_981 10y ago
"Teams like you describe are considered to be in "operational overload" and are actively dismantled by senior leadership.." -In theory, maybe... But with the expectation to stay in said team for atleast a year or two before switching teams and the associated difficulty in actually doing it, I think it is a pretty bad postion for said SREs to be in.