fair. I used to think that too, but I find at least for golang, the sota models write tests way faster than I would be able to. tdd is actually really possible with ai imo. except of course you get the scaffolding implementation (I haven't figured out a way to get models to write tests in a way that ensures the tests actually do something useful without an implementation).
Your final sentence is interesting. I'm not a strict doctrine adherent, but in TDD, don't you write some minimal test, then implement the system to pass the test?
yes, but I find it hard to constrain it to a minimal implementation. what usually happens is it writes some tests, then an implementation, and then according to the thinking, makes some modification. it works with a relatively precise prompt, but starts to go a bit off the rails when you say things in broad terms ("write tests to ensure concurrency works, and the implementation to ensure said tests are correct")
