The Stack Overflow annual survey of developers came out this month, and it has a lot of interesting data points in it. There is a lot that I wish was different about their questions/methodology, but one thing caught my attention. Docker, Kubernetes and similar tools (Ansible and Terraform are in there at lower percentages, for example) make up more of the responses than can be accounted for by people with โDevOpsโ in their title.
Sometimes by a lot.
That means we have a fair number of developers that are doing DevOps, but who arenโt DevOps team members. Yeah, there are a few systems admins in the ranks of the respondents also, but not enough to cover the discrepancy. If every respondent that was in DevOps and sysadmin roles used Kubernetes, there would be just enough to cover the number of respondents that said they used Kubernetes โextensivelyโ over the past year. It’s unlikely that all of them are Kubernetes specialists. And that doesnโt touch on Docker, with a whopping 40% of respondents saying they use Docker extensively. Any developer with recent experience can explain away Dockerโthough โextensiveโ is a bit strong for your average developerโs usage, it is becoming part and parcel of development, using containers to host dev environments, test, even build tools. And, of course, some deployments. But 40% is still a lot.
So, if your title is developer, and youโre using deployment tools on a regular basis, go ahead and call yourself DevOps. Thatโs not the only criteria, but if you were going to pick one, the breadth that using deployment tools represents combined with the implication that there isnโt an ops person worrying about that type of thing makes โuses deployment toolsโ a good stand-in test.
To the nearly 18% (20% of pro developers) of you using Yarn, I tip my hat. I used it for a couple of years early on in its life, and am happy to say I do not need to use it any longer. I assume your usage is not tied to Hadoop and that it has greatly improved over my 2015-2016 experience. Still, yโall rock, just by definition of using it to get resource scheduling down. It ainโt easy.
Across the board, the number of DevOps/Ops tools that make these lists is amazing for a developer survey โ nearly 9% of respondents use Ansible, and nearly 9% use Terraform. There is undoubtedly overlap, so the actual number that uses one or the other is less than 18%, but still, nearly one in 10? Thatโs huge. And thatโs DevOps or Ops, not purely developers. Regardless of title.
And thatโs been a hallmark of development since the field took offโdoing what needs to be done to deliver software. This is just another iteration, and youโre rockstars, regardless of title. You keep delivering apps that run the businessโlet them call you whatever they like. Money talks; titles are pretty much meaningless. Not like youโll retire on a title, but bonuses or stock grants? Those you might retire on.



