Debugging Is Mostly Thinking, Not Commands

Solid framing around debugging as a thinking exercise rather than command memorization. I'm curious though -- you describe moving from trial-and-error to mental modeling, but in practice with distributed systems (multi-container setups, service meshes), the mental model often needs to be built from observable state because the system is too complex to hold in your head. Do you think there's a threshold where systematic observability tooling (structured logs, traces) becomes the thinking framework itself, rather than something separate from it?