What? The earlier you detect you're on the wrong course and fix it, the less logic is built on the bad code and so the _cheaper_ it is to resolve. Also tests should be in the spot of detailed design, driving the design, not at the end. Pretty much 100% of your anti-patterns would be avoided by using tests correctly at the right time.