My wife is a vibe-coder, now what?
My wife has never written a line of code. She doesn't know what a function is. She thinks "React" is something you do after someone scares you. Last week she built her first app.
Not "played with a demo." Not "clicked around in a template." Built an app.
She sat down with an AI coding assistant, described what she wanted, argued with it when it got things wrong, and three hours later had a working prototype. No Stack Overflow. No tutorials. No bootcamp. Just a person with a clear idea and a tool that could turn that idea into software.
I watched it happen and had one thought: everything just changed.
AI is just a programming language that speaks English. I mean that literally. You describe the state you want. You describe the behavior you want. The machine translates it into code. My wife proved that in three hours.
But "accessible" does not mean "automatic." My wife did not say "make me an app" and get handed a finished product. She spent hours refining it. She had to think through user flows, make design decisions, reject bad suggestions, and push back when the AI wandered off into nonsense. She was the product owner, designer, QA tester, and creative director — roles she defined as she went, same as always. The AI was the developer who happened to work for free.
The AI had zero taste and zero context for why the app should exist. It had endless opinions about implementation details nobody asked for. Creativity and taste still live with the human. The AI just removed the annoying wall between "I have an idea" and "I have a working thing."
This is the part that actually excites me: engineers are not coders anymore. We are managers.
I used to spend most of my day wiring up forms and tables. Input validation. CRUD endpoints. The same boring glue code every product needs and nobody dreams about writing. Necessary work, sure. Soul-crushing if you are honest about it.
Now I hand that work to agents and move on.
My workflow looks nothing like it did two years ago. I spin up multiple agents, each working on a different piece of the system. One builds the API layer. Another writes tests. A third refactors the module I have been avoiding for months. I review the output, correct the dumb parts, and spend my actual time on architecture, system design, and deciding what should exist in the first place.
That is engineering management. The reports just happen to be AI agents instead of people.
The skill set changed. It is less about remembering the exact syntax for a PostgreSQL upsert and more about knowing whether an upsert is the right call at all. Less typing. More judgment.
And the work that remains is the good stuff. Architecture questions. Scaling questions. Product questions. The creative part that got us into engineering before a decade of Jira tickets trained us to accept form fields as a lifestyle.
The gatekeeping is over. Good.
Some engineers hate this. We spent years memorizing the incantations, and now somebody who has never written a function can produce working software in an afternoon. I understand the grievance. I don't share it.
But my wife's app works. It does what she needs. She saw a problem and built a solution. The fact that she used AI instead of learning JavaScript does not make the output less valid. It just makes the old gate look ridiculous.
The floor has risen. The baseline for "who can build software" now includes anyone with a clear idea, enough patience, and enough taste to know when the machine is lying to them.
The ceiling did not drop. Complex distributed systems, performance-critical code, security, data integrity — that stuff still needs deep expertise. AI can help. It cannot replace the judgment you get from years of building things, breaking them, fixing them at 2 a.m., and remembering the scar tissue next time.
The gap between "I can make a simple app" and "I can architect a production system" is wider than ever. But the first part is no longer locked behind whether you learned to code.
That is not a threat to engineering. It is the job finally getting honest.
The keyboard was never the point. The point was building the thing.
References: