Implementing multiple libraries and languages, long a pain point for developers, might finally be less painful than it once was.
A recent study of more than 1,000 software developers in 50 companies by software distribution platform JFrog found a drop in those who rated this as the most challenging aspect of their drop, with the number diving from 37 percent to 12 percent.
This finding comes despite the fact that three-fourths of the developers who took part in the study are using at least two technologies in the development process. In fact, 27 percent said they were now using between four to six platforms, while eight percent are using eight or more.
All that diversification points to the potential benefits of using DevOps — a system for collaborating amongst various members of an IT and software development team.
DevOps = Higher Performance
Similar research by Puppet Labs looked at operations from 20,000 respondents involved in such efforts. It presses the point that DevOps-style collaboration leads to significantly higher rates of return for those who are willing to not just work together, but engage in a specific strategy for doing so.
For example, such “high-performing” IT organizations have 60 times fewer failures and recover from catastrophe far more rapidly. Also, they’re 168 times faster at deploying code than other lower-performing peers.
Additionally, with 200 times the shorter lead time, you’ll have happier team members and customers with much more rapid deployments of code. The necessity of such a system is going to vary with every organization, but some of the evidence indicates that a close matching of goals and expectations within a development team can certainly pay off.
Another key element of the research focused on something that is a constant battle for those seeking to grow or further improve their business: Burnout.
It’s one of the constant battles for any manager or colleague, as it can grind a project to a halt when one or more members hit that breaking point. It takes on many forms, be it just exhaustion, reduced work performance or potentially greater absence due to illness. Yet all that code isn’t going anywhere.
Much of the advice from the State of DevOps report is what you’d expect to find from any research that addresses a work culture, such as encouraging managers to listen to employee concerns, develop a positive environment and find effective leaders.
But there’s a practical goal, which is to avoid the necessity to put out the fires that often churn up at the last minute in an IT environment.
Find ways to plan out work and limit the last-minute issues as much as possible so that the team doesn’t feel like it’s constantly rushing from one crisis to the next. It sounds easier than it is to implement in practice, but with new tools and collaboration schemes available, the new year might be a promising time to implement some effective changes.
For More Information:
- Mapping Our Way to Accountability
- Survey Says, 'Show Your IT Team a Little Love'
- Agile + Scale - DevOps = Predictable Doom
- The Million Dollar DevOps Question
Title image by Oliur Rahman