“No Duh,” say senior developers everywhere.
The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.
Usefulness really comes down to which model is being used. I’ve noticed most developers choose GPT for Copilot because that’s what they are familiar with (or they often don’t have a choice due to company policy). I recommend to try Claude Sonnet. How it works is true magic.
But I agree, repetitive tasks is what it should be used for. Planning is still programmer’s job
GPT has been quite hit and miss for me, but Claude is usually quite solid.
It needs micromanaging, otherwise it will do bad design decisions and go off on unrelated side quests. When micromanaged it’ll get you to that MVP very fast.
The trap is that you need to be able to find the errors it makes, or at least call them out immediately. Trying to have co-pilot fix it’s own mistakes is usually a neverending prompt-cycle.
It can summarise big code bases fast, and find how things fit together a lot faster than me. It’s been very useful when being thrown in head first into a new project.
Claude Sonnet? so you enjoy being lied to on a daily basis because that’s all you’re getting from Claude. Claude Code is alright but using Claude.ai you might as well just throw a dart at wall to get a solution on something.
It amplifies a person. If you smart, it will help. If you dumb, it will make you dumber.
I used to work with a pretty great coder.
Everything he’s done in the last 6 months has been trash
Big code assist energy
Yeah, one of my colleagues leans on it too hard and it’s really undermining his actual talent.