Code got cheap. These five skills didn't

A coding agent can write in minutes what used to take an afternoon. We use agents at Hexerize every day, and the speed is real. But the work didn't go away. It moved.

In Sonar's developer survey, developers said 42% of the code they commit is already AI-generated or assisted, and they expect that to reach 65% by 2027. As it grows, the hard part becomes everything around the code.

Deciding what to do, handing it over, checking the result and explaining it used to be a manager's job. Now anyone working with an agent does all four, because an agent is a very fast teammate that still needs managing. It's happening from the other side too. In LeadDev's 2026 leadership report, 37% of engineering leaders said they're doing more hands-on technical work. The line between the two jobs is moving from both ends.

Here are the five skills we think matter most now.

1. Deciding what's worth building

An agent will build almost anything you ask. It only knows about your users what you tell it.

The people we build for mostly reach the web on a phone, often on mobile data, so a heavy page costs them real money. If we asked an agent for a video at the top of our home page, it would add one. We draw a moving background in the browser instead, so there's no video to download. That call comes from knowing who's on the other end.

2. Checking the work

In the same survey of over 1,100 developers, 96% said they don't fully trust AI-generated code, but only 48% always check it before committing. Sonar sells code-checking tools, so it has a stake in that result. We still believe the gap, because we've been in it.

An agent once checked our blog pages and reported no problems. It had been looking at the loading screen. The report sounded just as sure as a correct one would have. Now we watch tests run in an open browser window, and we look at the page ourselves before we believe a report.

3. Teaching people to check

Newer developers used to learn on the small tasks that now go to an agent, and the early numbers are worrying. Using US payroll data, Stanford researchers found that employment among 22 to 25 year olds in highly AI-exposed jobs is about 19% below where it would be if it had kept pace with people the same age in less exposed jobs. Experienced workers show no comparable gap. The researchers are clear that this is a pattern, and doesn't prove AI caused it.

Whatever the cause, nobody becomes a senior developer by watching an agent work. If you're training someone, give them the checking. Have them write the tests an agent must pass and the list of what "done" means, then go through the result together. Working out how something could fail teaches you more than writing its first draft.

4. Handing work over properly

An agent can't guess what you left out, and neither can a new teammate. Say what the work is for, what it mustn't touch and what finished looks like.

Then write down what you learn. Our agents don't commit or push until we say so, and if we correct one the same way twice, the correction becomes a written rule.

The same goes for people. If you fix every problem yourself because it's quicker, you become the slowest part of the team, and nobody else learns how.

5. Explaining it in plain words

On DropAsecret, a voice mask shifts the pitch and shape of your voice on your own phone, before the voice note is uploaded. That's accurate, and it means little to most people. "If you use a mask, we never receive your real voice" tells them what they get. Say what changes for the person listening, and leave out how you did it unless they ask.

Be just as plain about what you don't know. We can't say how software teams will work in a few years, and neither can anyone else. You can admit that and still say what you're doing now and what would change your mind.

One thing to try

Writing code still matters. You can't judge, check or explain what you don't understand. It just isn't the slow part any more.

The next time an agent finishes a task for you, note how long it took to write and how long it took you to be sure it was right. That second number is the one worth getting better at.