Software engineers got hit by AI disruption before most industries had time to prepare. Business Insider spent weeks interviewing developers, collecting survey data, and tracking the story in real time across a six-part series called The Great Coding Reset. Here is what they found.
The pace of change was faster than anyone expected
In early May, a concept called tokenmaxxing went mainstream. Companies set up internal leaderboards and encouraged engineers to use AI as much as possible. The tokens, as the series put it, flowed.
Within weeks, the narrative flipped. Uber’s COO said spiraling token costs were hard to justify. Amazon shut down its internal AI leaderboard. By June, the same companies pushing aggressive AI adoption were focused on reining in ballooning budgets.

Engineers are not a uniform bloc
The series pushed back on the binary framing that AI either destroys all jobs or creates a productivity utopia. The reality was messier.
Some engineers worried about losing the parts of their work they enjoy. Others spent weekends happily building with new tools. One developer told the reporters he gets more done with AI but stays wary about giving it too much control. A survey respondent said AI made their job worse in many ways. Another said it let them solve more complex problems while still feeling in control.
Junior developers face the biggest open question
Many engineers now spend their days reviewing AI-generated code and fixing its mistakes rather than writing from scratch. That shift has changed hiring criteria: companies increasingly vet AI skills alongside traditional coding ability.
The harder question is what this means for people starting out. Senior engineers tend to get the most from AI because they already have the technical depth to evaluate what the model is doing. If AI absorbs the debugging and simple feature work that once built junior-level skills, the path to that same depth becomes unclear.
The wider workforce should be watching
Software engineering got the AI reckoning first. Developers responded by learning new skills fast, leaning into the more human parts of the job, and in some cases moving into different roles where they felt they could have more impact.
The series notes there is no guarantee other white-collar jobs will be as exposed. Code is right or wrong. Most other work is messier and harder to automate cleanly. But the lessons about flexibility, adaptability, and identifying what makes your work genuinely hard to replace apply well beyond engineering.
