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.
Any conversation
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.
my wife is concerned that my job search will not be fruitful due to my use of ai to build and orchestrate my json and latex resume and cover letter build pipeline. it has not changed much since I initially built it almost 20 years ago. there are only so many ways that the core metadata can be assembled for presentation, yes?
New in agenttop.dev : panels open in your . ๐คนโโ๏ธ
โข Any panel can now split into its own pane, live, beside the table.
โข Works with all the popular multiplexers: , , ๐ฎ๐ป๐ฑ ๐ธ๐ถ๐๐๐.
โข run a panel on its own: agent-top mcp, agent-top slow, agent-top fails, agent-top advice.
โ The # MCP panel also lists the orphaned MCP processes that outlived their agent and are still eating memory.
