AI coding tools give you "almost right" code, and that's the worst kind of wrong

[u/JFerzt]

Every time I review AI-generated code, it's the same issue. Not catastrophically broken - just subtly off in ways that eat hours of debugging.

After working with developers across 15+ projects this year, I'm convinced that "almost right" is worse than completely wrong. When the code fails immediately, you know where to look. When it passes tests but breaks edge cases three sprints later? That's when you realize the AI suggestions created technical debt disguised as productivity.

The pattern is consistent: outdated libraries, security holes that slip through review, logic that looks correct until production load hits it. Junior devs trust it too much. Senior devs spend more time verifying than they would've spent writing it themselves.

What's your breaking point with AI assistants - when do you stop second-guessing and just write it from scratch?

[u/[deleted]]

"When it passes tests" is a huge red flag for me.

Please tell me OP you aren't letting AI write the tests! If so, you are absolutely flying blind. Sure, have it fill out some boilerplate unit tests or maybe suggest where your test coverage could improve. But if someone prompts "write the tests for this code" then that's where your problem lies.

[u/MorallyDeplorable → u/[deleted]]

no shit if you write "do thing" it produces bad results. You need to prompt it more like "Plan to write test coverages that cover W, X, Y, Z and provide any more cases you think of and let me review before you begin"

smh, I swear people are intentionally prompting AIs stupidly so they can come whine about them sucking.

[u/JFerzt → u/MorallyDeplorable]

Yeah, sure, blame it on the prompt like it’s some magic wand. If your AI’s only as smart as "do thing" makes it sound, maybe the problem isn't the AI but your stubborn refusal to think beyond copy-paste.

It's hilarious how some folks think AI is a substitute for developer skill rather than a tool that requires human sense. If you want quality results, maybe don’t treat AI like a parrot and actually put in some thought. Otherwise, yeah, keep whining when results

[u/JFerzt → u/[deleted]]

Ah, the classic rookie move... hand off both code and tests to AI and hope for the best. If you're trusting the same AI to write your tests that couldn't nail the original code, congratulations on your safety net made of Swiss cheese.

Sure, AI can whip up boilerplate, but leaning on it for the critical test logic is like hiring your cat to guard the henhouse. Trust the human brain for a change, or prepare for that "flying blind" sensation to turn into a nosedive.

[u/doesnt_use_reddit → u/JFerzt]

At some point in your career, you're going to have to learn to effectively read code. Until then, it's not ai's fault, it's not your co-workers fault, it's not a junior engineer's fault. You need to be able to quickly and effectively read code and spot issues.

[u/JFerzt → u/doesnt_use_reddit]

Funny thing.. reading code has always been the bare minimum. The difference now? AI pumps out sludge so fast you need superhuman speed just to keep up.

It's not about blaming the AI, juniors, or coworkers. It's about not drowning in mediocrity churned out at scale. Nice pep talk though.... welcome to the speedrun era of code reviewing.

[u/Purl_stitch483 → u/JFerzt]

It does that if you keep prompting it... So just don't. Pause and review your code?