Finally merged the jetpack PR in hallucinate.site โ now you can fly around!
Any conversation
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
I still don't get how now after AI coding there's people saying that contrary to common belief code wasn't a bottleneck and I realized that when I was starting to code at 10yrs ago when I was 15 and read it in a stackoverflow comment. I thought that was the common belief and still can't believe a lot of supposed senior programmers apparently believed so.
I notice that language models are much better at programming than at writing. This is largely because, in programming, they have a closed feedback loop that allows them to find errors. Writing is much more complicated because the feedback is much more diffuse and delayed over time. In fact, it is often not well-defined.
This #tome about #Tcl/Tk has me re-evaluating my plans to move to the woods to be a carpenter hermit.
Now I want to move to the woods and be a programmer hermit.



