Coding 2025-10-27
"Feels good to work on" isn't the same as "immediately useful", even on what is arguably an art project.
"Feels good to work on" isn't the same as "immediately useful", even on what is arguably an art project.
Oh yeah, I wanted to put all this stuff on a website...
At some point, this really should have a package. And tests. And source control beyond "I'm pretty sure the NAS is backing it up".
It's a little late to say this, but I swear it's not a pun whenever I say "base" or "based" and it's not referring to a numeric representation.
"Hey, I just got done undoing a bunch of premature architecture weirdness. Let's do more of that."
If you can get rid of some metaprogramming without breaking things, you probably should at least try.
Accidentally making progress on the prototype.
Deleting the Bad Code and writing the Good (Or At Least, Not As Bad) Code
I do not want to let myself get derailed, but honestly I probably should?
Making some weird problems for myself by refusing to consider approximate solutions.