I’m somewhat conflicted on principled TDD. Often when writing code I find issues with the specifications, sometimes serious enough that interfaces need to be redesigned. Or even more often, problems that were assumed to be simple turn out to be far more complex with lots of edge cases no one thought of when writing user stories, meaning that substantial refactoring has to be done. For the more extreme yet still frequent instances, these situations would mean not only throwing out the code implementation but also the tests. If you write the code first and test after, you throw out 1/4 of the code than you would in TDD (usually tests are several times longer than the implementation in solidity).

Any thoughts on how to manage these risks?