Alright, real talk moment. Last week I watched someone with zero coding background build a fully functional app in an afternoon. Working auth, a database, a halfway decent UI. Prompt in, app out. They were thrilled. I was thrilled for them. And also, if I'm honest, quietly having a small existential crisis in the corner of the room.
Not because I felt threatened exactly. More like — I spent actual years learning why guard let exists, why force-unwrapping an optional is basically playing production Russian roulette, why you don't just slap @State on everything and hope. And now that entire chunk of hard-won suffering can apparently be skipped with a well-worded prompt and a bit of patience. Cool. Cool cool cool. Love that for me.
The New Skill Isn't Coding. It's Knowing What You Don't Know.
Here's the thing that's been sitting weird with me: the app that person built works. It runs. It does the thing. But if it breaks in a weird edge case at 2am, they have no idea why, because they never had to build the mental model that would let them find out. They have the output without the map.
It's giving major "I summoned a shadow clone but I don't actually know ninjutsu" vibes. The clone can absolutely fight for you. It looks exactly like you. It even talks like you. But the second something goes wrong that the clone wasn't built to handle, you're standing there with zero chakra and zero idea what just happened, because you never did the training that would let you improvise.
That's the real shift, I think. It's not "can you build the thing." It's "when the thing inevitably breaks in a way nobody predicted, do you have literally any framework for figuring out why." AI is extremely good at producing working code. It is much less good at producing a person who understands why it's working, which is a completely different skill that doesn't transfer just because you were in the room when it happened.
The Uncomfortable Part Nobody Wants to Say Out Loud
Here's where it gets messier though, and I want to be fair about this instead of just being smug about my years of suffering like it was some kind of noble sacrifice.
A huge amount of what "understanding code" used to gatekeep wasn't actually that valuable in itself. Knowing the exact syntax for a for loop in three different languages was never the point — it was a costly proxy for the thing that actually mattered, which was being able to reason about logic and structure. If AI genuinely lets more people skip the costly proxy and get straight to building useful things, that's not automatically bad. Loads of us gatekept a skill that was mostly just "memorized enough incantations to get the compiler to stop yelling," and dressed it up as deep expertise.
So I don't think the honest question is "is it bad that people can build without understanding." I think it's "what happens to the people who only ever build without understanding, the moment something needs actual understanding to fix." Those are very different problems, and I think a lot of the online discourse conveniently blurs them together because "everyone's fine, don't worry about it" and "everyone's cooked, we're all doomed" are both easier takes than the actually annoying, nuanced middle one.
My Honest, Slightly Nervous Take
I think we're heading toward two very different kinds of app-builders, and the split isn't going to be "used AI" vs "didn't use AI," because basically everyone's going to use it. The split is going to be between people who used AI as a shortcut through understanding, versus people who used it as a scaffold toward understanding — same tool, completely different relationship to it.
The scaffold group asks why, even when the thing already works. They read the generated code like it's a stranger's PR, not a magic box. They break things on purpose in a sandbox just to see what the error actually looks like, so next time it happens for real they're not starting from zero. The shortcut group ships the working thing and moves on, and I get it, deadlines are real, but eventually the bill comes due, usually at the worst possible time, usually in production, usually on a Friday.
I want to be in the scaffold group. Some days I actually am. Other days I catch myself accepting a suggestion because it compiled and I had somewhere to be, and I have to go back later and actually sit with what it did, like eating my vegetables after I already had the dessert.
Okay, Your Turn, Don't Leave Me Hanging Here
So genuinely — where do you land on this? Do you think "understanding the code" is going to matter less over time, the same way most of us don't understand assembly anymore and it's completely fine? Or is this different, because the failure modes of AI-generated logic are weirder and less predictable than the failure modes of a compiler?
And be honest: when's the last time you accepted a suggestion, watched it work, and never actually went back to ask why?
Asking for a friend. The friend is, once again, me. I contain multitudes and also several unexamined, accepted suggestions.
This article was written based on my own experiences and opinions. AI tools were used to help with grammar and structure, but the story, ideas, and voice are entirely my own.
Top comments (0)