DevOps are people now.
We’ve long considered the term “DevOps” to be primarily about a process, specifically a melding of the workflow between the developer (the “dev”) and the administrator (operations or ops). Yet we’ve found at least a few hundred readers of Stack Overflow who identified themselves professionally as “DevOps.”
What’s more, the tool choice of these self-identifying DevOps differs markedly from the enterprise developer. And the split aligns along identifiable lines at that.
It wasn’t the only curious fissure we’ve observed examining the data surrounding the world of software development. While outsiders may think of the computer programming as a monolithic job description, the field is teaming with dualities: mobile versus enterprise, front-end versus back-end, embedded versus everyone else. Each has their own favored tool sets.
For instance, looking at the programming languages they plan to use in the near future, DevOps folks are much more likely to expect to use Python, Go and Ruby, compared to enterprise developers, who favor C#, Java and C++.
Python, Go, and Ruby are not surprising finds in the DevOps tool belt. Python is handy because DevOps is much more focused on orchestrating the use of multiple different applications together, which Python is good at. Go’s prominence comes from it utility to manage microservices.
Since developers building enterprise-level services are more likely to be focused on legacy applications, it is also no surprise that a higher percentage will continue to use Java and C# moving forward.
Mobile devs are from Venus, DevOps are from Mars
Specialization obviously focuses your attention on some technologies to the exclusion of others. For the most part, the hottest technologies are of interest to all developer types. However, as they start to become more widely adopted, developers are more likely to continue learning and using a language that is in line with their professional goals.
|Current Use||Planned Used|
With such a dramatic difference in skill sets and plans, it is no wonder that most developers are not enthused about learning about mobile application development trends. The implications of this may be wider than you think. With such a divide in interests, Apple will continue to face obstacles as it tries to gain use among developers. More importantly, with so much innovation occurring outside their ecosystem, mobile developers are at risk of lagging behind. Furthermore, as developers continue to program for Android and iOS, it remains to be seen if they will start to use languages that are more commonly known. If not, then it is likely that we will see more SDKs and methods to integrate applications.
The back-end and front-end never meet
Embedded system developers versus the world
Feature image via Pixabay.