|
|
|
|
|
|
by vtemian
415 days ago
|
|
|
I'm still searching for successful vibe coding examples. Each time I tried it, with custom rules, git, and all the best practices I found, it went amazingly well initially, and garbage afterward. Using the same technique, after a while, it generates a lot more shitty code than helpful. > So, it’s shit and you’ll spend a long time fixing it. It just takes more time overall to make it functional.
Fixing, debugging and improving vibed code takes more mental resources and time than just writing it from scratch. Also, there's the flow aspect. Each time you let it "vibe", you're losing the flow state that is important while creating and thinking about complex work. |
|
|
I'm wondering what this means.
Kind of by definition, you wouldn't be able to tell "successful vibe coding" from "successful coding", right? Unless someone announces it. And a quick look at the comments here, or any other thread with about AI & coding, would immediately tell you is a bad idea to announce.
There's a few things you just don't say on HN, because you'll be piled-on immediately: don't criticize Kagi, don't hint at being pro-cryptocurrency, don't announce you "vibe coded" something even if it's extremely successful, etc.
(The immediate downvotes on this is actually hilarious, and proves the point)