After vibe coding for the last week, I realized I really like to code, and I hate having to watch YouTube and scroll my phone while the ai generates slop.

Its a great technology and a time saver and I'm definitely thankful for it. But I need to figure out better flows with it, where I'm actually shipping quality products with it, while also not just wasting time scrolling nostr while the AI builds 10 features with 35 bugs.

Its the best and the worst feelings I've had for a piece of tech ever 😂

Reply to this note

Please Login to reply.

Discussion

i'm not sure Y but th@ makes me smile, t Y for sharing/*

It really feels like the honeymoon phase of vibe coding has ended, and everyone's stuck dealing with the slop they've generated or abandoning it.

I'm sure it's here to stay, we just need to figure out how to use it effectively. Building and abandoning apps doesn't feel like the best use for it.

For me, the best use isn't vibing whole apps, but vibing functions and tests.

Vibe coding is hit or miss. The new wow factor has faded away and people are realizing it's not building the prototype app that's hard, it's building something fully functional worth shipping that's the hard part.

Ai + back end app setup included = who ever does this first wins all the vibe coders.

I like to build slowly with it, give it specific feature or even just careful scaffolding instructions. Let it do the work of a 23 year old mid-level developer who has bothered to memorize all the autistic shortcuts and framework/library syntax that will be obsolete in 5 years.

Then I review the code, tell it to eliminate all the stupid exceptional slop code that is never going to get hit, and we iterate towards cleaner, modular, reusable solutions.

Yep! You'll figure it out. I burn through so many tokens just doing, "build this function like this..." more hands on than "implement this feature". Right now they still just don't seem to have the ability to process a "big picture" project. My main projects are nearly 1M lines of code, it's just not able to process anywhere near that much info when it can only read a few dozen lines of a file at a time in most agent tools right now.

Right now, they are more suited for moving the pen while you watch them and tell them what to write. At least for me. Id rather spend tokens working really slowly in a positive direction, instead of having it over-confidently build entire features poorly, break things, then have to delete it all and start over myself.

I just want to make me faster.

This is exactly how I feel about vibecodingâ€Ķ thanks for putting it into words