Kirk@startrek.website āØ22ā© āØhoursā© ago CWA is the example I always point to as to why vibe coded software doesnāt make sense for broad use. CWA updates are slow (but detailed) which inspires many folks to āforkā it with vibe coded apps, but since CWAs last update in Feb, several vibe coded ācompetitorā projects have risen and fallen.
Iām starting to say vibe code is write only.
Like they used to say about Perl, indistinguishable from line noise.
Basically unmaintainable without super strict coding conventions, submitters taking personal responsibility, a strong, well thought out overarching architecture, and most importantly, someone with a great knowledge of the project to approve merges. Vibe coded forks to add one or two features have none of that.
This is why GitHub is littered with slop projects that havenāt been touched since they were made. This is why an ungodly amount of technical debt is accruing as managers with a hard on for lines of code or āfeaturesā force devs to unwisely use AI coding tools all the time. There will be a reckoning, and itās not far off.
Thatās a great way of putting it. I think in the future it will be helpful for when folks have some personal specific need. But for anything approaching even the simplest infrastructure it just doesnāt work.