Test Driven Development

This is TDD fundamentalism, and I mean that as a compliment. It enforces the red-green-refactor cycle with zero wiggle room: write a failing test, watch it actually fail, then write minimal code to pass. The iron law is no production code without seeing a test fail first, because a test that passes immediately proves nothing. If you write code before the test, you delete it and start over, no exceptions. It systematically dismantles every rationalization for skipping steps, from "I'll test after" to "deleting work is wasteful" to "I already manually tested it." Opinionated to the point of being confrontational, but that's exactly what you need when building the discipline. Use this when you want TDD done properly, not TDD-flavored development.