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.
Any conversation
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
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.


