Well I just got back from work, ate dinner and saw that Claude is still running. So now I have 24 hours of logs to read…
This is definitely a consideration and I think this is one of the most valid arguments against AI code in general. That being said, maybe I’m naive, but Claude has been testing it’s own code for the past 24 hours, so I genuinely question if code written by human developers has anywhere near the same level of rigor or testing.
I do get your point though, and I do mostly agree with it. It is just a bit hard for me to believe given what I’m currently watching. That also being said, I had Opus 4.6 review a codebase I was writing with it and it said it didn’t find any bugs, and then Opus 5 said it was absolutely filled with them. So… Maybe I’m being dumb.
So often when I hear people talk about how AI coding doesn’t work or is bad, I hear them talk like they are sitting there hovering over the code with a broom like an angry Karen.
It makes me wonder if people swatting it with a metaphorical broom and trying to be overly controlling is some part of the issue people are having or there really is some big issue I am not catching because I have blinders on. I rarely have significant issues getting it to do what I want, though it might also be the language and size of code base that I am working with. I’m really not sure.
I am really trying to think of a time this has happened for me and I honestly can’t think of anything that I can’t attribute to an edge case of something I was working with (like reverse engineering the video and control API for IPMI or iLO, so I could build an MCP tap for it), or something changing in a unexpected way, both of which would be equally, and probably far more likely with human written code.
If you have any examples I would love to hear them because I feel I’m either completely blind or tons of people are just really bad at using AI for coding.
I should probably make more of an effort to read the outputted code, but honestly I mostly don’t care unless it presents an issue, and this generation really hasn’t. Maybe the code isn’t hyper optimal, but I’m not trying to sit here and be pedantic when I want something to just work the way I tell it to. And after a few prompts it almost always does.
I generally find most software to be poorly thought out, slow and painful to use, and with some reasonable prompting, testing, correction and a tasteful amount of verbal abuse, I am able to get an app that does exactly what it is supposed to and works perfectly.
And if somehow there is a bug then it’s at most 3-4 prompts away from being fixed.
Alternately, I have wondered, is everyone just using something stupid like Haiku 4.5, Qwen Coder, or somehow lobotomizing their AI agent?
Anyway, my confusion aside, I appreciate your insight. I am just still finding myself unable to square this circle.
I will make a point to specifically have it look for that. I haven’t thus far, but it spontaneously called out one that we kind of built in on purpose for logging. Since so much of the filesystem is a rusted out flaming dumpster full of bullet holes, it really has no mechanism to protect data whatsoever and actively destroys it in a substantial number of cases.
Because of this I have needed to have Claude build fault logging in a few different ways so you can try to repair failed writes, determine which write failed(so you know which part of the parity is defective and can actually repair it), and generally just not yeet all your data.

Added logging:
I’m still reading the log of stuff since yesterday and I’ll post an update once I can parse that and my eyes stop hurting.