Earlier quoted context omitted.
> If you were a smart dev before AI, chances are you will remain a smart dev with AI. I don't think that's what people are upset about, or at least it's not for me. For me it's that writing code is really enjoyable, and delegating it to AI is hell on earth.
> For me it's that writing code is really enjoyable, and delegating it to AI is hell on earth. It's very sad, for me. Like I told someone recently - letting the LLM write my code for me is like letting the LLM play my video games for me. If all I wanted was the achievement on my steam profile, then sure, it makes sense, but that achievement is not why I play video games. I'm looking at all these people proudly showin…
My company pays me to build software that helps make them money. They don't care how I write that software as long as I do it fast and correctly. If that's by hand, I'll do it by hand. If vibe coding can get the job done, then I'll do that.
"Vibe coding" isn't just writing specs. It's ensuring that the vibe coding process doesn't introduce regressions, new bugs, etc. My boss writes specs for me, which, if I were to naively plop them into cursor or Claude code, would generate stuff that kinda works but not in a way that could be considered production ready. I plan, adjust the plan, generate, regenerate, refine. Could it be done faster by hand? Maybe. But it's the tool I've chosen for the job and the bosses are happy with it.