Honestly I super hate the word “DevOps”.<p>It doesn’t tell me anything about what you do; and it implies that sysadmins never used to code either.<p>There are people pushing “devops tools” but those tools used to be called deployment or build tools. The word is pointless ambiguity.<p>Additionally: the “title” was coined as the name of a conference to include developers. The actual intended job title (and original conference name) was “agile systems administrator” according to the person who invented the word (Patrick Dubois).<p><a href="http://blog.dijit.sh/devops-confusion-and-frustration" rel="nofollow">http://blog.dijit.sh/devops-confusion-and-frustration</a>
Unfortunately here in Germany the majority of “devops” is just a bunch of operations people who maintain terraform and ansible markup, no real dev involved.<p>DevSecOps seems to just be plugging sonarqube into ci pipelines and installing siem/wafs.<p>Is it really better anywhere else?
All the *Ops words are just attempts by people to name things. None of these attempts are particularly helpful, except perhaps as conversation starters.<p>I am not a "DevOps" engineer. I am a digital platform engineer, with specialization in writing code to connect things to other things.<p>When I talk to people outside of tech, I just tell them I'm a software engineer. It's close enough.
This is getting more and more ridiculous. I even heard about GitOps (ops that use git). What is next? CliOps?<p>Thank you for all the buzzwords without which poor sysadmin old me would've never heard of coding, automation, security, version control and so on. /s
To me, DevSecOps is mostly about seeing what tests can be done whilst not getting in the way of the development/deployment process too much.<p>That's not a bad thing and there's meaningful security testing that can be done with that strategy, but it's hard to cover all aspects of security testing in a fully automated DevSecOps pipeline.
The missing link here is that "Ops" should no longer be the traditional imperative, reactive approach to systems design and maintenance.<p>Ops in all three of these becomes the modifier. This is why most practitioners today will tell you that DevOps/DevSecOps/SecOps are less individual titles and more a cultural way of thinking and operating and that the philosophy is executed by engineers of all types.<p>It's important to remember the origins as well. Prior to DevOps, developers and operations teams were siloed in ways that hindered healthy growth in todays distributed systems and cloud environments. These "*Ops" terms were born of the necessity to impress upon people the importance of interoperability between traditionally isolated and independent departments.<p>*Ops is the natural progression of Conway's Law into modern engineering organizations.
I'm sure this is redundant, but since no one has mentioned yet:
"The Phoenix Project" and "The Unicorn Project" are awesome books for this, and I recommend them both in audiobook.
DevOps = sysadmin<p>SecOps = sysadmin has to apply the CIS/SCAP/whatever security template to the machine<p>DevSecOps = developer also has to apply the CIS/SCAP/whatever security template to their machine<p>It all ends up becoming marketing jargon for suits looking to follow the next big trend.
These are temporary job titles since most of the IT work these days comprise of gluing things together. I think these types of jobs will vanish with in the decade due to platforms like Microsoft's power platform or dynamics 365.