Yeah. I get that. For meatcoding I've often felt the tests were for other people, not myself. Until the codebase becomes big. My memory is leaky, I guess, so then its largely that I don't want to forget about interaction between component x and y.

With a team, or nonmeat coders, I will mess up at least once a day and I find my mistakes the costliest, but that's probably because I'm not letting go of control much

I create my fair share of regressions so I want/need tests. But I also want/need to keep max fear so I'm forced to compress and make sense of the code constantly.

k00b

The nice thing imo about unit tests is mainly to protect against regressions. The worst thing that ever happened to me though, and this was with humans, was that someone deleted test cases in a big update and I missed it in my review. This came back to bite me a few years later. So I'm super allergic to there not being tests, and to changes to tests without explanation. Especially with the bots.