Why developers miss cost
Most development sessions prioritize speed over reporting. That is normal. The problem appears when usage spikes, repeated requests, and background AI work keep moving while the developer is focused elsewhere.
The result is that cost only becomes visible after the useful debugging context has disappeared. That makes the problem harder to fix the next time it happens.