Exactly. This is the whole purpose behind the "spike" - make a branch, write a crap implementation of some code to help understand the problem, put it aside. Then go write the production version TDD style. Once you understand the problem, you can use TDD to create a good design to solve that problem.
Sounds crazy, but this is how I do everything I don't understand. And my second implementation is usually better than my first.
Comments
Exactly. This is the whole purpose behind the "spike" - make a branch, write a crap implementation of some code to help understand the problem, put it aside. Then go write the production version TDD style. Once you understand the problem, you can use TDD to create a good design to solve that problem.
Sounds crazy, but this is how I do everything I don't understand. And my second implementation is usually better than my first.
Or, in the words of Fred Brooks, build one to throw away. I'm always amazed at how prescient he was.
Unfortunately I find all too often that spike project finds its way into production for one reason or another. Now I only spike in Befunge.