4 ms·
So, there you have it. TDD is good if applied correctly, and only if you apply it 100% correct. And so it seems for LLM usage. If it doesn't work for you, then
by rootnod3 1y ago
So, there you have it. TDD is good if applied correctly, and only if you apply it 100% correct. And so it seems for LLM usage. If it doesn't work for you, then you are obviously doing it wrong according to many folks here. TDD is nice to catch refactoring mistakes, LLMs are nice to maybe do some initial refactoring on a small enough code base. And it doesn't mean that one precludes the other. But I haven't seen TDD put engineers out of work and neither should LLMs. Trust either model fully and you are in for a world of hurt.
- MoreQARespect 1y agoI would usually measure "TDD correctness" in terms of how closely the test matches a user story vs how closely it mirrors code implementation. The former is desirable, not common. The latter is common, not desirable.
- rootnod3 1y agoAnd with LLMs you'd have to measure how close the prompt is to a user story then. And how close its output is to the user story.