watch out for vibe coding death loops 

if you're building and fixing the same feature over and over you need to rethink that feature

vibe coding tests is different, I just keep hammering it til they all pass

Most of my casts (the good ones) are automated

Vibe coding is the best but I always ALWAYS have to clean up after it and move things around the way I like. 

Ever since I started noticing "oh this is going to be huge tech debt", leaving things lazy (aka vibe coded) just doesn't sit right.

Web3 consultant | senior engineer @lazertech | crypto dinosaur 🦖

ya no one talks about all the editing you have to do 

can't dismiss vibe coding entirely but saying that's all you need is misleading

"vibe coding" (or just ai coding) is fine if you are having it do stuff you are capable of without it for time efficiency. 

But its like the other day, cursor made a whole node project for me but populated the package.json with outdated dependancies. If someone is not a dev, they 100% will not catch that. (it was also annoying to fix)

I’m just using auto on cursor now. It’s pretty good but there’s some new nextjs stuff it misses. 

Using GPT 4.1 to build small games from scratch for fun and it’s surprisingly good. 

I rarely use it to build full features. I mostly use it to move code around.

I've tried a couple models now and the most annoying aspect is that they are all outdated and the fixes I make are always related to that. Maybe there exists a model specifically for coding that keeps up to date and trains itself on every new update that is released?

lol so annoying  

some stuff it just too big or important to mindlessly let AI do it