|
|
|
|
|
by pjmlp
4837 days ago
|
|
Usually this makes people go for very simple solutions without thinking properly what are the right data structures and algorithms for the problem at hand. I rather write proper designed code and write the tests afterwards, before delivering the code. |
|
If not, write a new test, make it pass. The naive implementation can be substituted with a different one easily since the tests guarantee correctness.
Generally though, since the "third leg" of TDD is refactoring, this ensures that the proper structures are going to be used in place as soon as they are actually needed.