Interesting, just finished reading John Allspaws 2015 paper from some debugging/problem solving at Etsy: http://lup.lub.lu.se/luur/download?func=downloadFile&re

Interesting, just finished reading John Allspaws 2015 paper from some debugging/problem solving at Etsy: http://lup.lub.lu.se/luur/download?func=downloadFile&recordOId=8084520&fileOId=8084521 http://lup.lub.lu.se/luur/download?func=downloadFile&recordO... (really slow.. sorry Sweden!) While it focuses on time tradeoffs and such during resolving outages, one of the major themes is that engineers/developers tend to use heuristics and past experiences to drive problem solving. I think as developers we tend to do the same, we look for common patterns for types of problems we've encountered. The debugger is just a representation of log analysis. So how do you teach those experiences? I think a lab-based approach with examples is probably the right course. Sun Microsystems used to have a Fault Analysis class they taught for Solaris.. It was essentially just a lab of 50 broken systems/scenarios that you had to diagnose and fix. I think more of that sort of thing earlier on would be helpful.