I've been on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines.
Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.
Any conversation
เถ
เถฏ เถดเทเทเทเถบ เถฏเทเท. เทเทโเถปเท เถฝเถเถเทเทเท เทเทเถธ เถธเทเทเถบเถเถธ เถดเทเถฑเท เทเถณ เถดเทเถบเถฑ เถฏเทเท เถดเทเถฏเท เถฑเทเทเทเถฉเท เถฏเทเถฑเถบเถเท. เทเทเทเถเท เถดเทเทเทเถบ (เถธเทเถบเท เถธเท) เถฝเทเถเถบเถงเถธ เถฑเทเทเทเถฉเท เถฏเทเถฑเถบเถเท.
Today is Poya Day. The full moon day of every month in Sri Lanka is a public holiday. Vesak Poya (May) is a holiday for the whole world.
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโโโโโโโ โโโ โโโ
โโโ โโโโโโโโโโโ โโโ โโโ
I needed to process 20,000 json files & 20,000 JXL files. I'm pulling together a website from them all. Anyway, started with emacs elisp to handle it all, just because I've not done that before. Went kinda ok, and I'm gonna use org-mode to export it all to a website (done that bit loads of times before).
In the end, I ended up breaking out my C programming skills (late 80s->nowish). It was a delight. Nothing more refreshing than writing raw code, that doesn't rely on 3rd party code/libs.
Error: Provider rejected the request (invalid_request_error, 400): Claude Code 2.1.75 does not support this model; version 2.1.251 or newer is required. Run
'claude update', or update the Claude desktop app, then try again. [request_id: req_011CedKqBRnC6Qr3m6nKEwNN]
Iโm not using Claude Code. This is how you drop the ball.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.


