I've had similar experiences with vibe coding small utilities. Theres something liberating about just describing what you want and iterating from there instead of getting bogged down in boilerplate. Though I do wonder if this approach will backfire when I need to debug these tools 6 months from now and have no idea whats actually going on under the hood. Have you had to go back and fix any of your vibe coded projects yet?
> Have you had to go back and fix any of your vibe coded projects yet?
Not yet, but you're absolutely right. Once a tool like this stops being front of mind, it'll fall right out of my head. It's a bit like driving somewhere versus being driven—I'm a lot more likely to remember how to get to a place if I have to actively navigate to it. If I'm in the passenger seat, all bets are off!
I've had similar experiences with vibe coding small utilities. Theres something liberating about just describing what you want and iterating from there instead of getting bogged down in boilerplate. Though I do wonder if this approach will backfire when I need to debug these tools 6 months from now and have no idea whats actually going on under the hood. Have you had to go back and fix any of your vibe coded projects yet?
> Have you had to go back and fix any of your vibe coded projects yet?
Not yet, but you're absolutely right. Once a tool like this stops being front of mind, it'll fall right out of my head. It's a bit like driving somewhere versus being driven—I'm a lot more likely to remember how to get to a place if I have to actively navigate to it. If I'm in the passenger seat, all bets are off!