That is good point. In my initial stages I like to explore the problem and tests just get in the way of being able to refactor everything very quickly. Maybe I

That is good point. In my initial stages I like to explore the problem and tests just get in the way of being able to refactor everything very quickly. Maybe I want to put some dirty implementation first and then once I think I understand the problem better quickly fix it? Maybe I want to start refactoring it without knowing where it exactly will lead me? The problem is tests do not help with these initial stages, they only help if you know exactly what you are doing. And once I am done with the initial stage I want to move to another problem. I don't like sticking with the same module to now do the documentation, tests, etc. Once something works and I am satisfied I move on.