Forrest Chen

vibe coding is real, just not in our repo

“i just draw a box and write ‘make app’ and boom—agent writes perfect code”

me and my team:

  1. spends 4 hours debugging a webhook that randomly fails in prod

  2. fights over whether a boolean flag should be is_active or active

  3. merges a PR that touches 182 files because Typescript

  4. writes actual logic that vibe agents refuse to touch

83 views

Add a comment

Replies

Best
David

One thing I don't really get is, so many people talk about vibe coding. But what real projects actually came from it?

Because I think it only counts as vibe coding if you don't touch a single line of code and only describe what you want via talking or writing. Otherwise it's AI assisted coding. And that works really well.

bak-je
@david442 I have created a web app called bak-je. I don’t know anything about next.js but I recently launched the web app using next.js though no one knows about it. You can check it out. https://bak-je.com
Sanskar Yadav

Vibe coding makes for great demos, but reality is hardly that clean.

It’s easy to talk about how AI writes perfect code, but real teams still struggle with edge cases, naming debates, and unexpected fails.
Most of the time, AI helps us move faster, it’s a fantastic assistant – but it doesn’t magically solve the messy and collaborative part of building.


Vibe coding probably only counts if the agent does 100% of the work, end to end, with zero human code edits. But so far, most shipped projects are AI-assisted, not AI-generated.

They still need engineers to untangle, review, and debug - which isn’t a bad thing. It’s just honest work.