
The wrong way (that most devs fall into) is to let the LLM generate the code, then to say “write tests for this”.
Its important to note that this problem is jist as prevalent with humans, Ive met countless devs that fall into this se trap with their own code and tests.
The whole point of TDD is writing the tests first, thats why its called test Driven development.
If your instructions emphasize TDD this definitely helps steer the agent better in the direction of “tests first, then make the tests pass”
This works especially well with a bug, if I tell the LLM “x bug report was found, first replicate the bug with a test, and then fix it” their efficacy skyrockets.
They’re pretty capable of first succeeding at replicating the bug, and once they have a test that does that they pretty much always can solve the problem if its not super super esoteric.











I thought like, canonically, avada kedavra fucks up your soul or whatever everytime you use it and it slowly corrupts you or something
So it has a downside.
Also, to work, you have to be able to mean it and basically be a psychopath for it to even work right.
Isn’t there explanations for why people dont just use it willy nilly?