In my experience over multiple months of greenfield and brownfield work, Claude doing TDD produces code that is 100% the quality and clarity I’d have achieved had I built the thing myself, and it does it 100% of the time
cadamsdotcom on Hacker News
100% the quality and clarity I’d have achieved had I built the thing myself
In the thread “Ask HN: Is anyone else sick of AI splattered code”
Helped: TDD approach with specific prompts to verify test failures.
Got in the way: Claude struggles initially with writing tests meant to fail.
… Reviewing the code is very pleasant because you get both the tests and production code and you can rely on the symmetry between them to understand the code’s intent and confirm that it does what it says. In my experience over multiple months of greenfield and brownfield work, Claude doing TDD produces code that is 100% the quality and clarity I’d have achieved had I built the thing myself, and it does it 100% of the time. Big part of that is because TDD compartmentalizes each task making it easy to avoid a single task having too much complexity.