Coding 2022-12-07
Not sure what "a good interface" even looks like in this context.
Not sure what "a good interface" even looks like in this context.
Maybe there's some kind of sampling bias, because the "obviously correct" code is usually easy to cover, so if I haven't covered a function completely, it's probably doing something horrible. Even if that's the case, I, um, don't care.
Just a little bit at a time, and it adds up.
It looks really complicated, but actually it can be very simple, unless I'm badly mistaken and it has to be extremely complicated.
Maybe I should re-evaluate the names before I work on the coverage? I don't know...
The bad names are still bad.
It'd be cool if this were obvious a priori, but a posteriori is better than nothing.
It's really gratifying that there weren't problems where there weren't supposed to be problems.
Discarding ideas that didn't quite work. Maybe I'll be able to re-satisfy their purpose, if I can show that I need to.
What does this code do? Breaks everything, probably.