cstanhope@social.coop ("Your friendly 'net denizen") wrote:
The only way to debug software, as far as I can tell, is to generate something that can be perceived with my senses that allow me to deduce what is wrong. So it's all print statement debugging, it's just sometimes my "print" statement might produce sound, flash LEDs, make something hot or cold, show plots on a screen, or it might (although rarely) be something generated automatically by a fancy debug tool somebody is trying to sell me.