[VaiPai15]

The framing of "is vibe coding a job requirement" conflates two things: the skill of coding-by-prompting, and the skill of knowing what you need to build. The second one is genuinely underrated. Knowing your problem well enough to describe a working solution, the inputs, the logic, the outputs, who uses it, is hard to automate. Generating the actual app from that description is increasingly not. We've been using Lyzr Architect (architect.new) for this; you describe the agentic app you want in plain English, it generates a full-stack React frontend + multi-agent backend and deploys a live URL. The "vibe coding" is more like a product spec conversation than an IDE session. The people who are best at it aren't coders, they're people who understand their problem deeply.

[embedding-shape]

You're describing two different jobs though, "what you need to build" is supposed to be done by the army of "product managers/owners" or whatever they're called, rather than letting the programmer do that, and the product managers/owners whole reason for existing is figuring out what to build, what not to build and how the thing should work.

If you end up having engineers do the work of product people, you'd end up with the typical "engineered mess" that might be very fast, and lots of complicated abstractions so 80% of the codebase can be reused, but no user can make sense of it.

Add in LLMs that tend to never push back on adding/changing things, and you wend up with deep technical debt really quickly.

Edit: Ugh, apparently you wrote your comment just to push your platform (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...) which is so trite, apparently HN is for people to push ads about their projects now...

[newswangerd]

I admit that vibe coding was kind of a clickbaity way to frame this, but I couldn't think of a better way to describe it. That might just underscore my ignorance in this domain.

One problem I personally have here is that I write code as a way to reason through and think about a problem. It's hard for me to grasp the best solution in a space until I try some things out first.

[zombot]

> + multi-agent backend

Does that mean you need AI subscriptions just to run your backend? That explodes costs even more than opaque cloud pricing. Sweet!