AI doesn't generate working products, that's still your job
Ranked #1 on Hacker News with 98 points and 77 comments.
Building software has never felt this accessible. You describe an idea in plain English, and within minutes, a working prototype appears on your screen. It has a UI. It connects to a database. It does the thing you imagined. For someone who has never written a line of code, that moment feels like magic. For someone who has spent years wrestling with compilers and stack traces, it's genuinely astonishing.
The prototype runs on your laptop. It breaks under load. It has no error handling. You find out that it may be leaking your API tokens. The data model made sense for the demo but falls apart the moment you add a second user. The authentication is held together with assumptions. There's a nagging worry whether everything is secure. You want to deploy it, and suddenly you're staring at a chasm between "this works" and "this is ready."
Getting to a prototype was never the hard part
Software engineers have always been able to get something running quickly. What took time was everything else: designing systems that hold up at scale, handling the cases users weren't supposed to encounter but inevitably do, building in observability so you know when things break, making deliberate decisions about data architecture that you'll regret less three years from now. None of that has changed. AI has dramatically accelerated the path to a first working version. It has not shortened the distance between a first working version and something production-grade.
The confusion arises because the feedback loop for the early part of the journey has become so fast and so rewarding. You ask, you receive, you see results. That cycle is genuinely exciting, and it creates the impression that the rest of software development must be similarly compressed. It isn't. The hard problems of building software were never primarily about writing syntax. They were about judgment: what to build, how to structure it, what to defer, when to say no. That judgement is what turns a vibe-coder into a sculptor, and an artisan. It is also what differentiates a prototype from a production-grade system.
The misguided case against learning computer science