The post discusses the missing skill in TDD called Behavioral Composition, which involves breaking a big complicated behavior into pieces, implementing and verifying those pieces, and having the confidence to work through the process. The post also describes a Toy Problem as an illustration of this skill. Finally, it highlights the role of tests in TDD, which is to restrict the scope of the problem and ensure that changes to the code work as intended.
Sort: