|
Also, the shift to SaaS also helped devops ascend. 24/7, 5-nine uptime expectations meant it was business critical for Google or Gmail to always be up. Honestly, to some degree, it is a rebranding which makes me sad. It's a rebranding because companies didn't change their company culture or change the job requirements. Devops is a new job consisting of sysadmin duties and developer abilities, and the time to actually work on things. Worse, as "on-call code janitors", they often are at the bottom of the totem at a company. (As a developer it is important to understand a company's totem. Google has engineers at the top of the totem; Salesforce has sales at the top. Apple puts design at the top.)Denying devops the time to do both makes you complicit in it merely being a rebranding. Denying the devops team both SWE and sysadmin makes for either a dev team or a sysadmin team but not a SRE team. There are companies that "get it". But there are far more that don't. We, as devops, have no system for "Apple's role id 1234 isn't actually a devops role. If you want want to be a sysadmin, whos paid well, please apply, but it's not the promised land where you, as an individual who wants to live in the CI/CD SRE promised land, want to go. Thus, it's ~meaningless everytime I see the string "devops" in a job posting because without further interrogation, I can't know if the job is dev, or ops, or devops. Which is where it actually counts. |