I feel like it has a lot to do with the ambiguity involved in debugging, and the fact that it is hard to teach. I have found debugging to be fuzzy and largely

I feel like it has a lot to do with the ambiguity involved in debugging, and the fact that it is hard to teach. I have found debugging to be fuzzy and largely based on experience, mental models, and internal (scientific method based?) approaches. There seem to be a relatively few debugging methodologies or frameworks. (ie in performance/systems realm there are USE, RED, ...?). I have only started to recently create a formal framework (a google doc I update after each incident) after 9 years of engineering experience! Not because I wasn't interesting in debugging, but it literally took 9 years worth of debugging incidents for patterns to start to become apparent to me (i work devops/system so when there is a general feeling of a problem I'm usually tasked with finding root causes). On a side note: so far the framework has been successful within my org and I hope to formalize it enough to write about it in the near future :)