Mar 24 (edited) • General discussion
If time is money, I was bankrupt
Vibe coding is so new and so wild west that it’s tempting to just push the limits. See what you can build. See what you can add. The list is nearly endless.
Before I shipped anything successful, I’d be working on a project and go, oh that’s cool, let me add that. Oh that feature looks great, let me throw that in too. And this. And this. And this.and on and on.
Soon I’d have these massive files packed with features. Then I’d find one bug and it would cascade. Feature after feature breaking because everything was tangled together like balls of string that were just thrown together. This is technical debt and it made the apps nearly unusable. And I couldn’t figure out how to dig myself out.
I had to scrap and start over. And it was hard to learn because…
I did it More than once.
The lesson: with vibe coding today, an important question to answer is not what are you going to build. It’s what are you NOT going to build. Because when you can do anything it’s tempting to do everything.
What’s a lesson you’ve learned the hard way?
1
2 comments
If time is money, I was bankrupt
powered by
skool.com/service-righter-5590
Build with Claude Code, Cursor, OpenClaw, Supabase & more. No coding experience needed. From zero to your first paying customer.
Suggested communities
Powered by