Hacker News new | past | comments | ask | show | jobs | submit login

I have doubts that testing is going to be the key to make vibe coding work for non-trivial projects. I'd focus on developing great well documented interfaces between components and keeping the scope of your agent under control.





Perhaps I wasn't clear, but I was referring to a small tool or a specific feature that, in my opinion, embodies your approach. Keeping the scope clear and minimizing cognitive load—through practices like code splitting—are essential. Implementing tests, whether unit, component, or integration tests, as part of your testing strategy, helps provide quick feedback on recent changes. As you would do it on a traditional codebase.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: