Much of what I do, in multiple fields, could be reduced to one skill: troubleshooting. I’ll define troubleshooting as systematically determining the cause of unwanted behaviour in a system, and fixing it. Troubleshooting is often learned tacitly, in the process of explicitly learning “the skill”. Troubleshooting is rarely discussed as a skill unto itself. But many features of an effective approach to troubleshooting are domain-agnostic. Realizing that I spend more time troubleshooting than I do ...