ATRIUMsearch → argument graph
DataVideo · 10:50 — 11:54

Heavy AI usage correlates with developers feeling their coding skills are diminishing and experiencing less enjoyment from their work.

Survey results show 59% of developers feel their skills are diminishing and 54% report less enjoyment from coding since adopting AI tools, with the two findings strongly overlapping in the data. ✦ AI generated

Scott Tolinski · Syntax · 2026-08-14 · original ↗

starts at this moment · 10:50

We asked developers, do you feel like your actual coding skills are sharpening, holding steady, or diminishing? 59% put their own skills on the diminishing side of things. As well as how much genuine enjoyment or flow do you get from coding now compared to before you started using AI heavily? 54% said they get less enjoyment out of coding than they used to. And those two things aren't separate findings, by the way. In the data, it's mostly the same people. The ones who felt like their skills were slipping were the ones enjoying it the least.

verbatim transcript · starts at 10:50

Transcript · around this moment

10:50diminishing? 59% put their own skills on the diminishing side of things. As well as how much genuine enjoyment or flow do you get from coding now compared to before you started using AI heavily? 54% said they get less enjoyment out of coding than they used to. And those two things aren't separate findings, by the way. In the data, it's mostly the same people. The ones who felt like their

11:14skills were slipping were the ones enjoying it the least. [music] And to be clear about this, wasn't like an assessment of their skills. This is just like what they believe about their own skills, right? >> I am a programmer, and a lot of what I was struggling with last year was I felt that I AI was ripping that identity away from me. And so now my workflow is

11:34essentially a conversation back and forth with a very, very smart junior dev. I to I layout like I I very intentionally try to pick something where I am still driving the work. I know what I want to accomplish. I have a pretty good idea how I want to do it. Let's start a subtask, flesh out my ideas. You go read a bunch of files and research and I'll point you to some other docs.

12:01Let's generate some architecture docs, some research docs. Let's go through the plan. I'll look at it and once I'm very sure that both both of us are on the same page about what I what I want to do. Now you go edit the files. And I actually still review most of the code myself. And so I'm very intentionally choosing a workflow that I know is not as fast

Around this claim