The less successful person didn’t write much code, and he had excellent reasons why: I’m too busy! The person who made the request can’t wait! I have 100 other things to do today! Nobody’s allocating time for me to write code!
Google has this fixed. SREs can only spend a maximum of 50% of time doing manual admin work.
Certainly wasn’t true when I was an SRE at Google, and the person on my team who documented everything he did manually, such that the first automated system for doing that work was called “Electric [hisname]”, was penalized for rolling up his sleeves to do the grotty work and logging things as Tom advocates here, while others who were all about parroting rules on how much could be in shell, etc, were studiously nowhere to be found in the aftermath of an Emergency Power Off.
I know which people I’d rather have on my team again. Tom’s article is excellent.
Google has this fixed. SREs can only spend a maximum of 50% of time doing manual admin work.
Certainly wasn’t true when I was an SRE at Google, and the person on my team who documented everything he did manually, such that the first automated system for doing that work was called “Electric [hisname]”, was penalized for rolling up his sleeves to do the grotty work and logging things as Tom advocates here, while others who were all about parroting rules on how much could be in shell, etc, were studiously nowhere to be found in the aftermath of an Emergency Power Off.
I know which people I’d rather have on my team again. Tom’s article is excellent.
Ah to be clear I have never worked at google, I just read that from an official source. (Think it was googles book on SRE)
Note: not about manpages.