In this post, we share the third of eight key findings. If you don’t wait to wait for the rest of the results, you can download the full survey report right now at the link below.
TL;DR overview
- Developers spend less than a third of their workweek (32%) actually writing or improving code — a clear indicator of how much developer time writing code is lost to non-coding tasks.
- Code management consumes 35% of developer time: maintenance (19%), testing (12%), and security issues (4%), with software developers alone spending 22% of their time on maintenance.
- In organizations with over 500 developers, maintenance time rises to 32% — suggesting that complexity compounds as codebases and teams grow.
- Reducing maintenance burden — especially for open source dependencies — represents the largest opportunity to recover developer capacity and redirect it toward building new features.
Finding #3: Developers spend more time maintaining, testing, and securing existing code than they do writing or improving code.
We wanted to use this survey to get a detailed view of how developers spend their time.
We gave respondents six categories in which to bucket their time and asked them to estimate the percentage of their work invested in each category.
While this might not be surprising to developers, it is perhaps disheartening to see that respondents spend less than one-third of their time writing new code or improving existing code (32%). Respondents spend 35% of their time managing code, including code maintenance (19%), testing (12%), and responding to security issues (4%). Another 23% is spent in meetings and on management and operational tasks.
Respondents spend 35% of their time managing code, including code maintenance (19%), testing (12%), and responding to security issues (4%).
Breaking the data down by job description gives us an even clearer view. Software developers spend 22% of their time just doing code maintenance. They also spend a higher percentage of their time writing new code or improving existing code (39%) and a much lower percentage of their time on operational tasks and in meetings (14%).
Not surprisingly, people who manage software developers spend twice as much time in meetings as do the people they supervise. DevOps engineers and managers spend even more of their time in meetings (34%), partly because they are facilitating communication between different teams. They also spend twice as much time (7%) responding to security issues, which will be of no surprise to those familiar with the DevSecOps trend.
We also asked respondents to share the percentage of the time they spend on code maintenance related to their open source dependencies. The answer is right on target with the results in a previous survey (25%). But once we look at the data by number of developers in the organization, it presents an even starker picture. In organizations with over 500 developers, the percentage of time devoted to maintenance activities rises to 32%, which might be due to maintenance issues becoming more complex as the codebase and applications get larger.
This data makes one thing very clear: there is a huge opportunity for organizations to find new ways to increase the percentage of time their developers spend writing code. What more can be done to make developers more efficient so they can spend less time on activities like code maintenance? When it comes to maintaining open source dependencies, a managed open source approach that offloads these maintenance activities to the project creators could have a big impact on returning some of that precious development time.