Asked Claude to implement a game based on a text quest book I played in 90s. Letโs see. Tried to play the original text, downloaded epub. Well, I died after 3 minutes in the game.
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.
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.



