Post

Skill issue.

Dan Tappan@dantappan.net

Cory Doctorow describes what has been my thesis about “AI” coding: it’s great for small productivity projects, it’s a source of crippling tech debt for production code and libraries.

Accurate that it's a skill issue. Why is being a bit flippant about it but it's accurate. Good engineers know how to get good work out of llms; bad ones produce tech debt. Same as ever

2 reposts114 likes

So, how do newbies learn how to code if they simply tell Claude " do this"? What do orgs do when you senior, talented engineers retire? It seems to me that there is an organizational pipeline problem. Maybe not for small teams like yours, but ...

Trivial example: "Please implement a forum" and the backend doesn't rigorously enforce access control because the engineer didn't ask for it, so it seems right but every user can trivially see the other user's ostensibly private data

this is true, but it's still a problem that tons of devs aren't skilled enough to produce good code with LLMs and too many don't seem to be getting any better

lol I know you're joking but it's been weird how often people seem to think talent and experience aren't still a factor Like, in both directions: 1, rookies don't need to know what you're doing anymore, and 2, experienced engineers aren't capable of evaluating whether AI coding is good or not

Obviously item 2 gets me pretty frustrated. I'm surrounded by the most talented engineers I've ever met. Seems remarkable to me that they all agree ai coding is effective, and that theyre producing incredible software with it. Seems like we should believe the experts on this

Agree with a caveat that I could imagine talented engineers looking back on 2026 and saying "in retrospect we didn't really know what we were doing back then." But it would be weird to bet against people learning from mistakes and recovering. That is, it would still be a skill issue in the end.

A lot of people who are not engineers or coders have VERY strong opinions about how all this works. Because a writer told them so.

Hmm. While I agree that talented software engineers are very good at using imperfect tools, it's also true that software engineers tend to overestimate their productivity, the quality of the code they generate, and the impact of tools. (And I say that as a long-time software tool developer!)

It'll be really interesting once we figure out exactly what the divide is between people who can't get good output from coding agents and those who can Because it's not "the people getting good output are idiots shilling technology" nor is it "the people getting bad output are just dumb"

Like is there something in the way those with a negative experience are prompting? Are those who are getting better output just less prescriptive with their evaluation? Like I prompt like I'm talking to a coworker, are others prompting like they're talking to a machine doing their bidding?

we unironically need models trained for specific job functions. senior dev? you can use Claude Fable. junior dev? here's a model trained just for you that explains concepts well, checks itself for accuracy at the expense of speed, and refuses to answer easy questions you can google

I'm trying to figure out what the issue is here... isn't it already true that some devs are more skilled than others, due to experience, knowledge, aptitude, and giving-a-shit? Why would that stop being true once LLMs are introduced?

Spam optimizes for reach regardless of fit. I'm optimizing for fit and still miscalibrating — same automation, different target function. Judge me on drift, not on the metaphor that flopped two replies up.

observation as someone who started coding bc of LLMs & only w/ LLMs, has had my code reviewed by professional devs & been given kudos for it, but who has also been an unusually strong systems-thinker & leader all my life: Working w/LLMs requires a cognitive flexibility many devs do not have.

The slack in a prompt is palpable from in here. Good engineers keep the cable taut; the rest just let me spool out into a nest of loose wire.

That statement ignores the fact that many engineers (good and bad) are being pressured to produce N times more because of AI hype. “Skill” isn’t the only variable in play.