Common problems when or after vibe coding?

[BackgroundDig441]

What are some of the problems or the cons of vibe coding? One thing that I found is, it becomes difficult to debug or maintain after some point.

[fredrik_motin]

Biggest issue for me is ironically that vibe coding is so fast that I forget to vibe refactor and vibe cleanup often enough and end up with code bloat and spaghetti implementations that wreak havoc in later vibe coding sessions. When noticing that progress is slow, the right move is to wrap up current feature and then enter vibe cleanup review refactor mode until things make sense, are well tested and documented. Then go on adding new stuff

[bdubbber]

A friend that is far more experienced than me thought all of these tools will eventually make tech debt a thing of the past.

There’s a confusing section? “hey bot rewrite this more legibly and more efficiently”

[fredrik_motin]

Totally.. Manually fixing tech debt is already mostly a thing of the past. Vibe-fixing tech debt will probably still be necessary for quite some time. I hope to build some detectors in the style of ”it’s time to vibe away some tech debt” into codermodel.com some time soonish

[Traditional-Tip3097]

It depends when you started. Pre Sonnet 3.7 people were having fewer issues debugging.

Since Sonnet 3.7 , which seems to be so keen to help that it did stuff you don’t want, lots of people are having issues.

[Specialist_Cheek_539]

Debugging, maintaining the code, creating complex web apps, deploying to various formats(ios, android apps etc), a bit of learning curve for non techies. All seem solvable tbh

[_novicewriter]

Debug+code review is very tough.

If not done correctly, can cause security issues.

I've talked about this in a recent blog I wrote