In my vibe coding process, most bugs arise because AI aims for optimal, over-engineered pre-abstraction and design. AI frequently misjudges the complexity of future environments, leading to numerous bugs that are incredibly difficult to fix. 😅Hardcoding, on the other hand, allows for rapid feature implementation and bug resolution.
These rules have proven to be exceptionally effective:
If a feature is repeated less than 5 times, hardcode it directly; do not abstract.
If a feature is repeated 5 or more times and is completely identical, a shared module can be created.
If a feature has a 20% (or more) variation, hardcode it to maintain customization flexibility
#vibecoding
Replies (2)
I've just been trying to get it to stop relying on compiler tools for code checking. "Okay that's done, now lets check it with npm run build. Oh I see the build is failing, let me take a look. Oh it looks like I named this function incorrectly, let me fix that. Lets check again. Great! Only 56 errors now, lets continue. Oh it looks like I also named this incorrectly, lets update all the places I used this function. Great lets run npm run build. Great! Only 55 errors now!"
No matter how clearly you write, and rewrite the instructions it still can't get even javascript code "right".
There will always be more bugs to fix in the future, until the bugs pile up like a mountain, and he will say we will just go away, and then do the bug fixing process all over again. 😂
