Have you ever inherited code, made a simple change, had it completely fail to work how you thought it would, and spent hours hunting down a subtle bug in your change? It might not be entirely your own fault! The previous developer may have laid one or more booby-traps for you to step into. (Then again, that may have been "past you"!) This talk will help you spot many kinds of such traps before you trigger them, and avoid laying them yourself.

There is code, so of course each example is in some specific language, but most of the concepts are language-independent. (Though some are more likely in certain languages than others.)

Agenda:
- What's a bug-magnet?
- Famous real-life examples, like Apple's goto-fail
- Other bug-attractive common situations, like complex code, long functions, lack of tests, etc.
- Less well known examples
- Theoretical examples I haven't actually seen
- General advice
- Tools to detect them and maybe suggest alternatives
- Wrapup