I found that even the concept of doing the "binary search" when debugging is an acquired skill. I often see people facing a vague (in a sense that it could be a

I found that even the concept of doing the "binary search" when debugging is an acquired skill. I often see people facing a vague (in a sense that it could be anywhere e.g. among multiple components or services) issue either think by analogy to previously seen issues without verifying; or offer various hypotheses that are random and unlikely/unwarranted (from "what if we just restart it" to "maybe RAM is defective and is corrupting the data"); or jump on a random correlate that may be spurious or actually a side-effect of the issue itself, without verifying it; or just get stumped. Just forcing yourself to think "how can I narrow it down [whether it's to one of many distributed services, or to 20 lines of code out of 200]?" / "what is the next piece of information I need?" greatly improves your debugging/live site skills.