I really like this article by Chelsea Troy in Functionize.
https://www.functionize.com/blog/improve-your-debugging-strategies/
Most developers know the standard strategy of debugging that she highlights. I would paraphrase her standard strategy term as "speeding through debugging with random breakpoints based on what developer believe is causing the issue." Like the author points out, this strategy is usually not the best unless you already know the the entire code base of the application or system. With the vast inter-communication among multiple apps, I doubt most developers today have this capacity to store an entire code base in human memory.
She defines another term called the investigation strategy. This strategy uses an existing algorithm to find the root cause of the issue like a binary search. The point isn't to list all the approaches to debugging but to understand that a better strategy is needed to improve your debugging skills. And, it should be language-agnostic as well as independent of any debugging tools (although it's helpful).
Thanks, Chelsea.