3 ms·
If anyone has links to maintaining a vibe coded (meaning you trust the LLM to some level as opposed to giving it a thorough review) product over a long period o
by alaoallaka 1y ago
If anyone has links to maintaining a vibe coded (meaning you trust the LLM to some level as opposed to giving it a thorough review) product over a long period of time I’d love to see that! As is it’s always like this - lines of code, test coverage %, # of commits, etc. Metrics higher ups and others who don’t really know how to measure quality software love to point too. The only metric that’s reliable is the code, but that’s not often shared for projects done this way. And when they are, they don’t live up to the hype.
I’m not claiming vibe coded projects don’t have a place. I’m skeptical that using English prompts can build a maintainable code base as well as using a programming language.
- lubujackson 1y agoNo links to share, by my approach is to create rich, up-to-date documentation that is structured positively for LLM prompt usage but also serves as breadcrumbs to the mental model of the product. When things change, have the LLM update the docs. Think of this as "document-driven development" in the vein of "test-driven development". The goal is to never lose the big or mid-level picture of things and allow the LLMs to careful adjust those, then implement the details as it sees fit.