So you've watched Part 1, right? I mean, you don't want to start with Part 2, because you'll miss all the preliminary discussion on the three laws. So, just checking.
Part 2 is where things really start to get interesting. First we look at the topic of incremental algorithmics, the notion that you can derive an algorithm, one step at a time, by posing a failing test, and then making that test pass.
As part of this process we'll learn one of the most foundational principles of Test Driven Development, the principle where the magic really comes from: as the tests get more specific, the code gets more generic.
And then...and then... Well, then we go and get ourselves stuck. Stuck is a technical term that means: "stuck." In TDD, when you are stuck, it means that in order to make the currently failing test pass, you've got to implement the whole program. It means there's no incremental step to take, no simple solution, no easy path.
So first we show you how to get stuck, because there's nothing quite so informative (and fun) as watching Uncle Bob fail. Then, we back up and show you how to get unstuck, and how to avoid getting stuck in the first place.
And then we're done. Uh, well, with Episode 19, that is. But that's just the first of many episodes we're going to do on Advanced TDD. So, keep watch for more!