Coding 2022-05-29
It does feel kind of good to break down functions to the point where the type signature makes it obvious what they "should" do, then just slap those primitives together.
It does feel kind of good to break down functions to the point where the type signature makes it obvious what they "should" do, then just slap those primitives together.
I wish this were the fun kind of code crimes.
The steps make sense, but there sure are a lot of them.
Some bits of this look a little suspicious, but it should be fine overall.
I'm kind of curious how intensely frustrating this code would be for anyone else to work with. Some of my process here has felt like how, if I'm not being careful when I do math on paper, the work ends up flowing in essentially random directions that only I can follow.
The sun is a deadly laser.
Remembering that "Oh, yeah! I implemented all of that stuff for a reason."
Awkward category switch mid-post, oh well.
Renaming modules is a necessary evil.
Hindsight is... not quite 20/20, but close enough.