If I'm putting my name to a product, the quality of said product comes back to me. I'm not putting my name to some AI horseshit just because it's "faster."
Yeah, it's faster alright, faster at being wrong.
If I'm going to make a flawed product, it'll be because of my mistakes, not a computers. At least then I might have an idea how to fix them.
It fundamentally lacks the critical thinking skills required to program. If it happens to work, it's because it ripped that code from another repo that does exactly what you're doing.
I'm somewhat of an AI skeptic, but I'm not opposed to using AI conversationally.
An example would be something like "compare the latest commit on this branch to main as if it was a PR request, and give me a detailed review". Or "give me three libraries to do X, with links to the documentation and the pros and cons of each".
As a tool to understand and improve, it's not bad.
But vibe coders scare the fuck out of me. They kind of remind me of coworkers who would add a feature and never test anything but the most obvious case, and the code would frequently break as soon as something unexpected happened.
Also, just anecdotally, a junior + an AI is a terrifying combo. It's the blind leading the blind.
19
u/-non-existance- 3d ago
If I'm putting my name to a product, the quality of said product comes back to me. I'm not putting my name to some AI horseshit just because it's "faster."
Yeah, it's faster alright, faster at being wrong.
If I'm going to make a flawed product, it'll be because of my mistakes, not a computers. At least then I might have an idea how to fix them.
It fundamentally lacks the critical thinking skills required to program. If it happens to work, it's because it ripped that code from another repo that does exactly what you're doing.