Earlier quoted context omitted.
No it's not you, I do get asked to be a sysadmin quite often. I have no idea why. It's not something I'm good at. I did for a short time in college to pay tuition a decade ago. I don't enjoy it. I never apply for it. For some bizarre reason, people ask if I want to be a sysadmin out of the blue. Drives me crazy.
It's not that bizarre, you write software mainly used by systems administrators. I used to work with one of the guys who wrote apache, and now work with a guy who wrote most of one of the popular NOSQL engines. And they both work as systems administrators. Not "useradd" systems administrators (although they are technically in that part of the org chart) but more like what Google calls "SREs." Rather than explaining w…
I liked OmniTI's description of a role akin to SRE and the progression through the web operations career path they identify: http://omniti.com/seeds/what-is-web-operations .
"This role is in no way fitting for failed developers, it is for developers/engineers that have outpaced their career path. One that has a deep understanding of how things work: a complete systemic view of general site architecture."