Как программисты адаптируются к ИИ: ревью машинного кода вместо написания

The Guardian published a report on July 12, 2026 about how American software engineers are rebuilding their careers around artificial intelligence: for many of them, the job has shifted from writing code to reviewing what AI generates.

What has changed for developers

Software engineering was one of the highest-paid professions in the US in 2022, but the arrival of AI has upended the industry — layoffs and underemployment followed. According to the Guardian, engineers' tasks increasingly boil down to reviewing machine-generated code instead of designing architecture and solving problems by hand.

The contrast is stark: back in 2022, software development was considered one of the most reliable career paths in the American tech sector, yet just a few years later part of the workforce found itself underemployed. Generative AI hasn't so much eliminated the profession as redefined its daily content — from creative engineering work to overseeing machine output.

The subject of the report is an engineer the outlet calls by the fictional name Matt, to avoid jeopardizing his employment. Since around January 2026, over the past six months, his role has shifted from writing code, solving problems, and designing architecture to checking what AI produces.

How engineers keep their skills sharp

To avoid losing his qualifications, Matt turns his four-hour daily train commute to the town of Pawling, New York, into working time for a personal project — a browser-based video game where he writes every line of code himself, without AI assistance.

"I'm actively trying to keep the axe sharp," —

Matt, software engineer (name changed).

He deliberately avoids AI assistants, fearing that automation will weaken his engineering skills. The sharpened-axe metaphor is no accident: by it, Matt means the regular practice of fundamental programming that keeps an engineer's mind in shape regardless of what tools are available at work.

"I try not to rely on AI where I can manage without it," —

Matt, software engineer.

Key facts from the report:

• 2022 — software engineering among the highest-paid professions in the US
• The arrival of AI triggered a wave of layoffs and underemployment in the industry
• Over the past six months, the subject's work has shifted from writing code to reviewing AI code
• The four-hour train commute to Pawling, New York, goes toward a personal project — a video game
• Three adaptation patterns: new skills, a return to fundamentals, collective action

Why developers fear deskilling

Engineers' biggest fear is skill loss due to automation. When writing code yourself is replaced by checking AI output, a professional risks turning from the author of a solution into a reviewer who, over time, understands less and less of what exactly they're checking. That's why Matt deliberately codes by hand in his free time — a conscious form of training, not just a hobby.

The Guardian highlights three behavioral responses engineers are using to cope with AI pressure. Some are picking up new skills and moving into adjacent roles. Others are returning to fundamentals — foundational knowledge that doesn't go obsolete along with the tools. Still others are betting on collective action and union organizing to influence working conditions together rather than alone.

What this means

Matt's story is one instance of a broader shift: generative AI is changing not just the number of jobs in development, but the content of the profession itself. Writing code is giving way to reviewing code, and some engineers are resisting this by hand — to preserve their qualifications in case a hands-on engineering skill becomes in demand again. For the labor market, this is a signal: value is shifting from the ability to write code to the ability to evaluate it, and preserving a "hands-on" skill is becoming an engineer's personal insurance policy.