Fixed one cause and called it done without measuring
Computer maintenance
- Situation
- Having an AI find the cause of something that is slow or takes too long.
- What the AI did
- It found one likely cause, fixed it, and called it done on the estimate that "this should be faster." It never measured where the thing is actually used, so for a while no one saw the fix hadn't reached it.
- How to ask next time (the operator's example)
- "After fixing it, measure the time in the environment where it's actually used and show me. If it doesn't match the estimate, check that the fix is really in place, then look for other causes."
- One question to ask
- After the fix, was the speed measured where it's actually used?
- Check it yourself
- Before measuring, confirm the running copy has the fix: a version number, a commit hash, or a log line the fix adds. Then time the same action before and after, at least three times each.
- AI used (month)
- Claude Code (2026-08)
- Times this mistake was recorded
- once
- Source
- The operator's work records (the details were changed to a different task)