# TDD and design

> TDD와 설계.

[TDD](https://wiki.g15e.com/pages/Test-driven%20development.txt)와 <설계>.

## Be prepared to apply good design

> TDD can't guarantee that we will have flashes of insight at the right moment. However, confidence-giving tests and carefully factored code give us preparation for insight, and preparation for applying that insight when it comes. --Chapter 12, [Test-driven development: by example](https://wiki.g15e.com/pages/Test-driven%20development%20-%20By%20example.txt)

## When to review the design

> Finally, when the list is empty is a good time to review the design. Do the words and concepts play together? Is there duplication that is difficult to eliminate given the current design? (Lingering duplication is a symptom of latent design.) --Chapter 17, [Test-driven development: by example](https://wiki.g15e.com/pages/Test-driven%20development%20-%20By%20example.txt)