If you're at all familiar with Test-Driven Development, you've probably heard "Red, Green, Refactor" as the three stages of the process. This translates to the steps: write a (single) failing test, write code to make it pass, and refactor. You may have also heard claims that "TDD improves your design", or "TDD reduces bugs [to zero]", or "TDD means all code is tested", however, TDD does none of these things unless you know what to pay attention to and know how to refactor towards better design._x000D_ _x000D_ If you watch an experienced practitioner do TDD, you will see a lot more activity between the three steps, not to mention the thought behind the work that you can't see._x000D_ _x000D_ In this talk, we'll explore what to look for during those three seemingly simple steps, and learn heuristics that you can apply throughout the TDD process.