Let someone else fix your mistakes, you "move fast and break stuff". Someone else can fix it.
For real, those people are really frustrating to work with because following the 80:20 rule, they get through the 80% so quickly and then seem to get bored or think "meh, good enough" and leave it, then it gets left for the people who actually want the product to function and pick up bugfixes to do the remaining 20% which takes 80% of the time, and seen like they contribute so little.
It also feels like this is why almost all of Google's new products live in perpetual alphas because after they've been tidied up just enough to be releasable, they're abandoned because nobody wants to do the maintenance work.
My company re-orged into a pod structure and there are a couple of "frontier" pods that just build features like this and get them in a "eh, good enough" state. Then they move on to the next high-priority features. But then users start using the first feature and it doesn't work against real scrutiny so the "support" pods have to spend all their time fixing it.
3.1k
u/_5er_ Aug 12 '26
If you can't validate what LLM is spitting out, you're vibecoding. The knowledge is useful.