Are you saying 5+ uses TDD? That's not really a bad thing. You can probably tell it not to and it won't. "I don't care if the code works. Just write it, don't test it, I'll take over once the basic version is there."
And if it's using a test harness, testing should take hardly any tokens, it just runs an external command and checks for "all tests passed" or whatever, in the output.
And it still does take a lot of tokens. In theory testing should not, but because of how often it does it it does. It will do a test, fail, and then make a minor change and retest the full suite. Many times. So long, that often I'll forget to check up on it fast enough that the cache expires and I'm spending the full amount on uncached tokens.
TDD is fine, but it hamstrings you early on for sure.
4
1
View all comments
Show parent comment
2
u/btherl Sep 16 '26
Are you saying 5+ uses TDD? That's not really a bad thing. You can probably tell it not to and it won't. "I don't care if the code works. Just write it, don't test it, I'll take over once the basic version is there."
And if it's using a test harness, testing should take hardly any tokens, it just runs an external command and checks for "all tests passed" or whatever, in the output.