Coding 2023-01-29
The concept: simplicity itself. The execution: twelve-dimensional summoning runes engraved on the surface of a hypercube. Like, anyone would look at this and go "this code is kind of confusing" and I KNOW.
The concept: simplicity itself. The execution: twelve-dimensional summoning runes engraved on the surface of a hypercube. Like, anyone would look at this and go "this code is kind of confusing" and I KNOW.
The problem I want to fix with this system is not that other people "aren't smart enough to use it" (and even if I agreed with that statement, it'd still be a me problem), but that it currently "expects" the end user to be able to read my mind.
Questioning the need for still more of the code. Which is a good impulse, but I have to be careful following it.
I needed to put even more thought in.
Let's wrap this stage up and see what it takes to cut a release!
Why use two classes, when you can use two classes and a Protocol?
I think I may have regressed coverage on the future topic, but, um, that's a Future Max problem.
Some of the weird stuff I ran into would have made a good post. Too bad I'm super tired.
Talking about these test rewrites like I'm a speedrunner. "Yeah, I've got a potential 12-second time save on my hands here"
I should maybe have expected some trouble from making all of these changes on adjacent lines in different topics.