vibe coding is amazing until the codebase gets big enough to bite back
first ten thousand lines flew. now the model keeps making changes that break things it cannot see. I think there is a size where you have to slow down and architect.
i love that this is just practical and not hype
wait how did you actually get that working
the eval first mindset is underrated, nice to see it here
tried, failed, tried again, finally works, can confirm
ok now do the version that handles errors
i would add: log everything, you will thank yourself later
this should be pinned
i would love a follow up on the cost side of this
what model were you running for this?
how is this holding up in prod?
had no idea you could do that, mind blown
how much did this cost you in tokens to figure out
i was skeptical but the example convinced me
ok this is actually clever, well done
finally someone said it
stealing this approach for work, thanks
what is the failure mode when the tool call times out?
finally someone said it
what model were you running for this?