How exactly are you using AI? Are you from 2023? If the AI cannot compile, lint, or type check it’s outputs with deterministic tools, you’re straight up using it wrong. I have a compiler for a reason, I want the AI to use that, not it’s vague memory.
When it comes to missing context, that’s (in most cases) on the developer calling it. It cannot have context that you do not give it. If the hyperspecific reason that module A is built weird (some insane legacy customer request maybe) only lives in the minds and hearts of developers having worked on it 3 years ago, that’s a failure of documentation, not the AI. A human could not have done better. Obviously, there’s limits to everything, but in my personal experience 95% of issues with AI agents would’ve have likely happened with a freshly onboarded human too.
The definition of vibe coding has shifted a bunch of times. I will agree that any non-developer using it for anything even remotely important/dangerous is asking for trouble. But a developer who knows the possible pitfalls can get pretty freaking far.
For me, the biggest fear is that noones educating/hiring juniors anymore. As a senior, that’s job security, but it will still fuck us over once we run out of old people that know what vim is.
How exactly are you using AI? Are you from 2023? If the AI cannot compile, lint, or type check it’s outputs with deterministic tools, you’re straight up using it wrong. I have a compiler for a reason, I want the AI to use that, not it’s vague memory.
When it comes to missing context, that’s (in most cases) on the developer calling it. It cannot have context that you do not give it. If the hyperspecific reason that module A is built weird (some insane legacy customer request maybe) only lives in the minds and hearts of developers having worked on it 3 years ago, that’s a failure of documentation, not the AI. A human could not have done better. Obviously, there’s limits to everything, but in my personal experience 95% of issues with AI agents would’ve have likely happened with a freshly onboarded human too.
The definition of vibe coding has shifted a bunch of times. I will agree that any non-developer using it for anything even remotely important/dangerous is asking for trouble. But a developer who knows the possible pitfalls can get pretty freaking far.
For me, the biggest fear is that noones educating/hiring juniors anymore. As a senior, that’s job security, but it will still fuck us over once we run out of old people that know what vim is.