201
Claude Code Swarms (addyosmani.com)
submitted 5 months ago by [M] to c/aicoding@programming.dev
202
My AI Adoption Journey (mitchellh.com)
submitted 5 months ago by [M] to c/aicoding@programming.dev
203
204
205
206
207
Agentic Engineering (addyosmani.com)
submitted 5 months ago by [M] to c/aicoding@programming.dev
208
209
 
 

TL;DR

So, what's the verdict? Can AI replace an experienced developer for debugging?

No, of course not. AI is very good at pattern recognition, and it can be very, very useful. It will do exceptionally well on standard stuff: schema validation mishaps, forgotten null checks, common runtime errors, you've seen it for yourself already. Personally, my debugging almost always starts with the LLM these days. With literally the prompts above: "here's what's happening, this is the log, fix it". Half the time, it manages to do that.

But even if the fix works, I always retrace it step by step and make sure it's the actual root cause. If the fix doesn't work, however, I almost never iterate with the LLM, other than asking it to find me something in the repo. As you've seen, half of its responses in this case will be very confident hallucinations.

210
211
212