AI is eroding my coding skills, and I don't care

By

Tagged: AI

63% of developers in a Syntax survey say their coding skills are diminishing. Mine are too. Here is why it doesn't worry me, and which skills I still keep.

On November 14, Scott Tolinski posted a clip from a talk with this question:

63% of developers say AI is eroding their coding skills. Does it matter?

Scott Tolinski's post on X, with a frame of his talk and a bar chart of the survey answers

I’m one of the 63%, and my answer is no.

Where the 63% comes from

The number is from the Vibe Health Check, a survey Syntax ran from July 31 to August 28, 2026. 3,593 developers who use AI heavily answered it.

One question asked them to place their coding skills on a scale from 1 (sharpening) to 5 (diminishing):

Coding skills: sharpening or diminishing?02004006008001000120014001 Sharpening3 Steady5 DiminishingAnswers

2,279 people picked 4 or 5, and that’s the 63%. Only 445, about 12%, said their skills are getting sharper.

It’s a survey about how people feel, and nobody’s skills were tested.

My JavaScript is rusty

I taught JavaScript for years, in blog posts, courses and handbooks.

Today my JavaScript is noticeably rusty. I can’t point to a moment when I blanked on something. It’s a feeling, and I trust it, because I stopped writing code by hand.

With other languages I never got to the point of having something to lose. I ship Mac apps written in Swift, and Answer Keeper came out today. On November 13 I released Footage Ferry for Windows, written in .NET and WinUI 3.

I couldn’t write those apps by hand, and I don’t care.

I also never read the code.

Skills always expire

In the replies, Ryan Florence compared it to knowing that zoom: 1 fixed a bunch of layout bugs in IE6. Nobody thinks that’s still important to know.

Scott and Wes Bos said the same on Syntax 1051. The Internet Explorer workarounds and clearfix hacks they learned are worth nothing today, and React changed under them many times.

I agree with them. Skills in this job have always expired, and writing syntax from memory is the latest one to go.

The skills I keep

Some skills I can’t let go.

SkillDo I still need it?Why
Writing syntax from memoryNoThe agent writes it
Reading codeNoI never read it
DebuggingYesAn agent can go in circles on a bug, and I have to get it out
ArchitectureYesI need to know how the pieces fit before any code is written
Taste and product senseYesI decide what’s worth building, and what good looks like

Debugging looks different when you don’t read the code. When an agent goes in circles on a bug, I give it better evidence: logs, screenshots, a way to reproduce the problem.

For Mac apps I set up a test VM where agents launch the app, take screenshots and click through it. The agent sees the bug with its own eyes, and I don’t have to describe it.

Who feels the loss

I think most of the 63% are attached to the craft, and they confuse it with the value of what they deliver.

The same survey has numbers that point this way. How hard people use AI barely changes the answer. 64% of those who often keep prompting past the time they meant to stop feel their skills diminishing, against 60% of those who rarely do.

What changes it is pressure. The survey groups people by two things: if they feel pressure to produce more because AI makes it possible, and if they keep prompting past their stopping point on their own.

Who sets the pacePeopleEnjoy coding more than beforeFeel their skills diminishing
Outside pressure only56412%69%
Both1,48424%67%
Neither26833%39%
Own pull only17346%48%

Enjoyment goes the same way. 68% of the people who feel their skills diminishing enjoy coding less than before. Among those who feel sharper, it’s 30%.

The survey is clear that these are associations and say nothing about the cause. Still, the people who feel the loss most are the ones pushed to produce more while enjoying it less.

I work for myself and I pick what I build, so I don’t have that pressure. I think it’s a big part of why rusty JavaScript doesn’t bother me.

Should you still learn to code?

It depends on your goal.

If you want a career as a software engineer, you need to learn to code. If you want to ship a product, you don’t.

People worry about juniors, who might never build the skills the rest of us are now losing. I think the entry-level job as we knew it is going away, so I don’t see it as the same problem.

I still learn every day, but I learn different things: less syntax, more about products, systems and how to direct agents.

Build what you couldn’t

To the developers in the 63%, my advice is to build what you couldn’t build before.

I’m a web developer. I now have a catalog of Mac apps and a Windows app, in languages I can’t write.

Pick the thing you never had the hours or the skills for, and build it.

Want me to talk about your product? You can sponsor this site.

Related posts about ai: