Test with confidence, code with clarity

Your home for mastering Test-Driven Development through real-world katas and expert guidance.

TDD Buddy Logo
Latest Lights Out · Part 3 / 3 Lights Out, Part 3: The Hill Climb

Kata Catalog

Practice TDD with a curated set of real-world katas, each with clear requirements and test cases.

Browse Katas

Guides & References

Learn best practices, naming conventions, and advanced TDD techniques from industry experts.

Explore Guides

Interactive Learning

Discover the TDD Gears model and learn how to apply TDD principles in real-world scenarios.

Learn More

Why TDD Matters More in the AI Era

The bar for "good tests" just moved. Agents made it non-optional.

  • A flat loop repeats. Part 1 named the lights-out state. Part 2 earned the trust. Neither post claims the pipeline improves. Part 3 does.
  • Selection pressure is the improvement mechanism. Without a signal to steer by, an unattended loop reproduces its own outputs indefinitely. With one, it climbs. The signal design is the whole game.
  • Demand gaps beat engagement as a topic signal. Queries with impressions and no clicks name unwritten posts. They cannot be gamed by writing more of what already ranks; they can only be answered by writing what does not yet exist.
  • The voice spec is constitutional. Engagement never gets a vote on how anything is written. Every future gain the loop finds has to arrive through the topic gate; the voice gate is unreachable from the reward signal by design.

Read the argument: Lights Out, Part 3: The Hill Climb

The Bar Moved

Old bar

Tests exist and pass. Good enough for humans with context.

New bar

Scenario names · builders · domain types · ubiquitous language. The test suite is the interface agents operate against.

TDD Gears

Shift gears based on context, not habit

TDD Gears model showing Low, Medium, High, and Reverse gears for test-driven development

Low Gear

New territory. Build context. Small steps. Learn the shape of the problem before solving it.

Medium Gear

Patterns emerge. Apply design principles. Let the tests guide you toward better abstractions.

High Gear

Known patterns. Follow existing architecture. Move fast because the structure is already proven.

Reverse Gear

Wrong direction. Back up. Delete the test. Try a different approach. This isn't failure — it's steering.