[shelajev]

If the code generation quality is so good you trust it to generate your verification system. You might as well write the tests yourself, and generate the actual implementation.

This way you're in control of what it means the code works, and formalize the acceptance criteria. Instead of feeding it a potentially incorrect implementation, and asking it to come up with a set of requirements what it should actually do.

[kevinlu1248]

I feel like at least for me, when I want to build fast, writing the implementation and having AI generate the unit tests to double check and catch edge cases is easier. I also don't use the unit tests as a verification but just to ensure the util functions don't deviate.

Writing unit tests is also more boring so I prefer writing the implementation.