Debugging to Programming is like porn to internet: it accounts for the majority of consumed time, yet almost never discussed. It is almost never an official part in university/college training, and rarely even asked about at job interviews.

How might a systematic debugging course look like? Can we define it as an engineering discipline? Can we extract some core principles that are valid across platforms and technologies?

In this talk I'll survey some of the (admittedly very thin) accumulated research, share my personal answers - and hope to dedicate time to listen to yours. We'll do 1-2 examples as time permits.