On "vibe coding"
Karpathy named the way I already build my spare-time tools. Here's where I do it and where I don't.
Back in February, Andrej Karpathy tweeted about a new kind of coding he called vibe coding, where you "fully give in to the vibes" and forget the code even exists. Six months later the term is everywhere, and half of what I read about it is people arguing over whether it's the future or a disaster.
I've stayed out of the argument because the tweet just described something I was already doing. My retrieval setup got built this way. So did a handful of small tools I use every week. I describe what I want, look at what comes back, and keep talking until it works. I couldn't have built any of it two years ago, and I'm still not an engineer now.
Where I draw the line is anything other people depend on. My spare-time tools have one user, so the cost of a mistake is mine and it's small. But anything going in front of a team, or that is production code, or is handling real data for a company, should still get reviewed by a human I think. At least for now. Maybe that'll change as time goes on.