I'm personally still in the "smarter autocomplete" phase when it comes to LLMs, as I don't trust the vibe-coded "agents" and the outputs they produce to control

I'm personally still in the "smarter autocomplete" phase when it comes to LLMs, as I don't trust the vibe-coded "agents" and the outputs they produce to control my computer. But that aside, this part stood out to me: > I don’t even look at the code anymore - I describe what I want to Claude Code, test the result, make some minor tweaks with the AI and if it’s not good enough, I start over with a slightly different initial prompt. Honestly, does the author and anyone else using this workflow find this way of working enjoyable? To me programming is not entirely about the end goal. It's mostly the small bursts of dopamine whenever I solve a particular problem; whenever I refactor code to make it cleaner, simpler, and easier to read; whenever I write a test and see it pass, knowing that I'm building a safety net to safely refactor in the future. And so on. Yes, the feeling of accomplishment after shipping a useful piece of software, be that a small script or a larger part of a system, is also great. But the small wins along the way are the things that make me want to keep programming. This way of working where you don't even look at the code, but describe the system specs in prose, go back and forth with an extremely confident but highly error prone tool, manually test the result, and repeat this until you're satisfied... doesn't sound fun or interesting at all.