|
|
|
|
|
by ChuckMcM
4520 days ago
|
|
I suspect if they had called it Architecture Driven Development (ADD) rather than Test Driven Development (TDD) it might contextualize better. Basically what the author explains is that you can design an architecture top down from simple requirements, deriving more complex requirements, and then providing an implementation strategy that lets you reason about whether or not you are "done." But that 'test' word really puts people in the wrong frame of mind at the outset. |
|