TDD is Backwards: Why Prototype-First Development Ships Better Software

Stop writing tests before you know what you're building You're about to build a new feature. The TDD playbook says write the tests first. But what tests? You don't even know what the API should look like yet. You don't know if this approach will work. You spend 2 hours writing tests for an interface that you'll rewrite in 30 minutes once you actually understand the problem. This isn't learning. It's cargo-cult development. I've spent the last year building multiple production tools. I've built a