"I've also spoken with Googlers about their devops/SRE responsibilities and I've gotten the distinct impression that what is advertised as being the organization's "best practice" is not in fact the common practice."…
"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…
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…
"I've also spoken with Googlers about their devops/SRE responsibilities and I've gotten the distinct impression that what is advertised as being the organization's "best practice" is not in fact the common practice."…
"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…
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…