@@@@@@@ @@@@@@@@ @@@ @@@ @@@@@@@ @@@ @@@@@@ @@@@@@@
@@! @@! @@! !@@ @@! @@! @@! @@@ !@@
@!! @!!!:! !@@!@! @!! @!! @!@ !@! !@! @!@!@
!!: !!: !: :!! !!: !!: !!: !!! :!! !!:
: : :: ::: ::: ::: : : ::.: : : :. : :: :: :
Any conversation
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.
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.
The best Mcp server I have as Claude Connector is Emacs running on my Homeserver. It has one tool - eval-elisp. Using it Claude can do almost anything. My top 1 pinned chat is โRun agent-start-claude-code using HotterEmacs in dir โฆโ - after that I have a ready to use remote-controlled session running on my homeserver.

