Engineering teams spend only about 16% of their week building new features, with 79% citing code maintenance as a major time drain, according to Chainguard's 2026 Engineering Reality Report. The post argues that developer experience (DevEx) should be treated as a capacity strategy rather than a perk, with measurable impact on roadmap delivery. Key findings: 88% of engineers report tool-switching hurts productivity, teams with high automation report dramatically more energizing work (94% vs 67%), and AI-assisted PRs are 2.6x larger but have only 32.7% acceptance rates vs 84.4% for manual PRs. Practical recommendations include tracking time-to-build, build/deploy friction, feature-to-toil ratios, and tool satisfaction — plus starting with a two-week friction-logging exercise to identify and fix the highest-frequency pain points.
Table of contents
The Real Cost of a Bad Developer ExperienceTool Sprawl Is a Tax on AttentionComplexity Is What Happens When the System Outgrows the MindAutomation Separates the Energized from the ExhaustedAI Does Not Fix Friction; It Magnifies ItWhat to Measure If You Want to Treat DevEx as CapacityThe Practical Playbook for CTOsThe Bottom LineReferencesQuestions this post answers
What percentage of their week do engineers actually spend building new features vs maintenance?
Engineers spend roughly 16% of their week building new features, while 79% cite code maintenance as a major drain on their time. The remaining time disappears into maintenance, upgrades, patching, vulnerability triage, CI failures, and context switching. Chainguard's 2026 Engineering Reality Report, based on 1,200 engineers and technology leaders, found 72% say demands on their time make it difficult to find space for new feature work. Engineering leaders tracking where time actually goes find the breakdown on daily.dev before it shows up in missed roadmap targets.
What is the acceptance rate of AI-assisted pull requests compared to manual ones?
AI-assisted pull requests have an acceptance rate of 32.7% compared to 84.4% for manual pull requests. They are also 2.6 times larger than unassisted PRs at the 75th percentile. These figures come from LinearB's 2026 Software Engineering Benchmarks Report, based on 8.1 million pull requests from 4,813 teams. AI accelerates code creation but does not reduce downstream friction in review, integration, testing, and deployment. Teams deciding whether to roll out AI coding tools across their pipelines track adoption data like this on daily.dev.
How much does automation affect how much time engineers spend on energizing work?
Teams where the majority of common engineering tasks are mostly or fully automated report dramatically better outcomes: 94% say they spend most of their time on energizing work, versus only 67% in low-automation teams, with just 14% strongly agreeing compared to 43% in high-automation groups. Chainguard's 2026 Engineering Reality Report found 65% of organizations have reached majority automation of common tasks. Engineering managers building the case for automation investment find supporting data like this on daily.dev.