In the Era of AI-Generated Code, Why Is Product Design Still the Bottleneck?
This is quite interesting.
Recently, I came across an article titled The Problem with Vibe Coding: You Still Need to Know What to Build. To put it plainly, the title immediately resonated with me.
So, what is āVibe Codingā? In short, it refers to the fact that AI is getting increasingly proficient at writing codeāyou can give it a vague requirement, and itāll spit out a bunch of code. Sounds amazing, right? But hereās the catch: just because AI can write code doesnāt mean it can decide what code to write.
For example, if you tell an AI, āBuild me a social app,ā it might indeed generate a bunch of interface and feature code. But the real question is⦠what kind of social app do you actually want? Something like WeChat or Twitter? Focused on close-knit connections or random matching? No matter how advanced the AI is, it canāt make those decisions for you.
This is the pain point of āVibe Coding.ā The barrier to generating code has lowered, but the barrier to product design hasnāt budged. In fact, it might even be more complicated nowābecause everyone can quickly āmake something,ā but what they make could be completely off the mark.
The article introduces a concept called āSolutioning,ā which I find fascinating. It essentially means that future AI tools shouldnāt just write code; they should also help users clarify requirements and design solutions. In other words, shifting from how to write code to what to build and why.
Honestly, this is tough. Current AI excels at execution but struggles with āthinking.ā Ask it to code a login page, and itāll do it in a flash. But ask, āIs this feature even necessary?ā and it might just freeze.
This is actually a great topic for discussion. With Metaās layoffs and constant updates to XR tools, everyoneās talking about how āAI will revolutionize productivity.ā But I think the real revolution isnāt about AI doing the work for usāitās about AI helping us figure out what to do.
The low-code movement has been around for years, so why do many companies still struggle to adopt it? Because no matter how simple the tools are, business logic remains complex. Even if AI generates code at lightning speed, product managers and developers still spend endless hours debating requirements and weighing options.
Thatās why this āSolutioningā concept might truly be the next breakthrough. If AI can help us identify problems earlier, validate ideas, or even simulate the outcomes of different approaches, that would be revolutionary.
That said, many AI tools today are still far from this goal. Most operate on the principle of āyou tell me what to do, and Iāll do it,ā rather than āletās figure out what to do together.ā
In the end, donāt get carried away by āAI can write code.ā Code is just a toolāthe real value lies in solving problems. If AI only speeds up execution without improving decision-making, its ceiling will remain firmly in place.
(End)