Atlassian: Devs Bogged Down by Non-Coding Tasks
New research from Atlassian reveals that developers are spending an excessive amount of time on non-coding tasks, even in AI-integrated workplaces. The findings suggest that current tooling is not yet effective enough at automating administrative and collaborative overhead, creating a drag on productivity in scaling engineering teams.
The latest Atlassian research reveals a stark paradox: while 68% of developers report saving over 10 hours a week thanks to AI tools, 50% are losing that same amount of time to organizational inefficiencies. This means for many, the net productivity gain from AI is hovering near zero. The primary time-wasters are not coding challenges, but rather finding information across scattered documents and systems, context switching between tools, and adapting to new technologies. Developers are reinvesting the time reclaimed by AI into high-leverage activities. The top priorities for this newfound time are improving code quality, followed by developing new features, and enhancing engineering culture and documentation. This signals a strong desire among engineers to focus on the craft and long-term health of the codebase, rather than just shipping features faster. A significant disconnect is emerging between engineers and leadership. 63% of developers feel that their leaders don't understand their primary pain points, a sharp increase from 44% in the previous year. This empathy gap may stem from leadership seeing the time savings from AI without recognizing the persistent underlying issues that prevent those gains from translating into faster delivery. This environment presents a critical choice for engineers shaping their careers. The focus is shifting from raw coding output to a more strategic role. The "You build it, you run it" (YBIYRI) model is becoming more prevalent, expanding the developer's role to include the entire product lifecycle. This trend, coupled with the automation of routine coding tasks, places a premium on skills like system design, cross-functional collaboration, and a deep understanding of the business domain. For engineers at startups, this highlights the importance of building a strong engineering culture from the outset. Rather than solely focusing on individual productivity metrics like lines of code, successful teams are adopting frameworks like DORA (Deployment frequency, Lead time for changes, Mean time to recovery, Change failure rate) to measure team health and efficiency. A focus on developer experience is also critical for retention, with 63% of developers considering it a key factor in their decision to stay with a company. The rise of low-code and no-code platforms further underscores the evolution of the developer's role. These tools are empowering non-technical team members to build and automate, freeing up engineers to tackle more complex challenges. This doesn't eliminate the need for skilled developers; instead, it elevates their work to focus on architecture, security, and building the core systems that these platforms often integrate with.
