management doesn’t have a clear image of what a “developer” role should look like in their company. combined with In those companies, it’s easy for a dev to b

management doesn’t have a clear image of what a “developer” role should look like in their company. combined with In those companies, it’s easy for a dev to become someone who is officially “a developer” but with a bunch of semi-official hats. results in a similar story with Devops and it's younger brother, SRE. My job role officially changed from "Devops Engineer" to "Site Reliability Engineer" when I switched jobs two years ago and I'm lacking in finding ways of differentiating the two. It's seemingly become the default response now on Devops communities when someone makes a thread saying "I want to get into Devops, what do you do?" that the job role means 'whatever the company wants it to mean', which is how we end up with Devops practitioners and teams getting turned into kitchen sinks for dealing with anything and everything the feature development groups aren't tasked with because of a severely unchallenged assumption that the dev team brings in revenue, while the operations people consume it. An assumption that's never said outright-mind you, but the organization and delegation of work between the two domains of functional teams, IMO says it pretty loudly.