Coding 2023-02-03
"That's too obvious, there's no way it wasn't handled." Friend, I regret to inform you,
"That's too obvious, there's no way it wasn't handled." Friend, I regret to inform you,
Now I know what it feels like to write something that explains why something doesn't work, and it's probably opaque to anyone else.
Again, you will notice that these names only occasionally and glancingly, like, signify properties of the things they're supposed to represent.
There is still so much left to fix this up...
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.
I'm not saying this code is "the right way" or "a good idea". It's just what I came up with.
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.
Why use two classes, when you can use two classes and a Protocol?