Complacent developers outnumber unhappy ones in Stack Overflow's survey of 30,903

Burnout or tech fatigue led the reasons complacent developers gave, at 21% ^[3]. That makes it the largest single cause, but still a minority one. About 79% of the group gave some other reason ^[18], so a response aimed only at burnout reaches roughly one in five of them ^[3].

A skeptic would say complacency is a stable condition. A developer who is coasting is not writing a resignation letter, and a mood survey is not a turnover survey. On the published record, that objection holds. The reported results describe how respondents feel about their current jobs ^[2]; Business Insider's account does not say whether they intend to leave. I think the defensible claim is narrower. Disengagement is the largest of the three states among the 30,903 respondents ^[1][2]. Just under 78% did not describe themselves as happy ^[17]. What that costs in departures, we do not know yet.

Usage and trust pull in opposite directions in the survey. The heaviest daily users spend hours with tools that most respondents would not rely on for an important decision ^[5][13]. Stack Overflow's chief executive, Prashanth Chandrasekar, said developers' skepticism was becoming a "critical safeguard" as agents took on more work ^[16]. "Trust is not a given when it comes to developers," he said. "It is earned through transparency, source attribution, and rich technical context." ^[15]

The two developers Business Insider interviewed describe opposite results from the same tools ^[6][10]. Marc Backes, a senior software engineer at Directus, said the work has lost what he liked about it. "It's definitely less fulfilling," he said. "I always enjoyed drafting out the best ways to implement a new feature and really think about it." ^[6][7] Simon Willison, founder of the Datasette open-source project, said the tools made his work "a lot more fulfilling" by letting him take on projects that once might have needed a small team ^[10].

Their circumstances differ on one point that matters for management. Backes said the pressure does not come directly from his manager. It comes from an industry that treats writing or reading code by hand as "the old way" ^[8]. "If I don't 'keep up,' I will be 'left behind,'" he said. "And keeping up with AI is virtually impossible." ^[9] Willison said being his own manager shields him from many of the pressures employed developers face, though he still finds the pace of AI releases exhausting ^[11].

This quarter, an engineering manager has to choose between delivery speed and leaving the design work Backes said he enjoyed in developers' hands ^[7]. Moving that work to agents buys throughput now. Next quarter's result depends on whether the team's developers end up nearer Backes's experience or Willison's ^[6][10]. Willison puts his down to skill ^[12]. "Using coding agents well is a deep skill," he said, one that requires both software-engineering knowledge and experience with the agents, "and I have both." ^[12]