Coding 2023-01-13
Fortunately, I can scale back some of my ambitions.
Fortunately, I can scale back some of my ambitions.
I need to work through the use cases here, or I might accidentally come up with something really complicated.
Gradually discovering the form that the code "should have" been in.
"This class has a bad name. If I can get rid of the class, I won't have to think of a better one."
The names are less abstract, but they still feel too abstract...
This is going to make the implementation ever so slightly squirrellier than the Platonic ideal, but, um, tough.
It turns out there may have been a reason I haven't come up with a better name yet?
Finding problems, looking for solutions.
Starting to rework more names
Feature request if I ever work on NABTO seriously: type checking should provide some visibility into how it's reasoning, because where I am right now just feels awful.