The debug madness and turning it into a safe and successful discipline

Damn it, this can't be happening! Our program crashes, so we run it again - and it crashes again. It's a madness that afflicts programmers. I contend that the activity of debugging has an inherent tendency to cognitive breakdown. How can we resist its merciless pull, and turn debugging into a methodical, safe, successful discipline?

Daniele works for Divio where he helps make Python/Django easier to deploy on the web. He is a member of the Django core team and the Django Software Foundation board, trying to contribute back to open source software and its communities.

This will be a really interesting talk for any developer who has ever "broken a thing".

Hope to see you all there.