Mostly software
My current side project, the one that's been consuming my hobby-less time for the past 15 years or so 1 is a small programming language and associated tools. The language itself is called turo or turo-lang. This post is not about that project or the language, but about an emergent workflow which is quite interesting, and transferable to other projects. 1 it's on its fourth iteration now,…
This is pretty exciting. I heard about Kaparthy's Autoresearch only vaguely: it's a way of getting the LLM to run experiments on itself(?), running for long periods of time. It wasn't until I read David Cortés' autoresearch-pi skill that I understood the significance. The skill lets you give your coding agent an optimization target for some or all of your code, then it: comes…
I just found a neat trick. I started talking to GPT-5-mini. I had a relatively long set of back and forths, but in the end decided to go to a more powerful model. I'd like to speak to another LLM. Please give me a prompt getting the next LLM up to speed efficiently with all context and my choices. Use a fence block to make copying the prompt easier. This prompt is entirely unremarkable, but for…
1 I don't know if I'm saying something so obvious that no-one even bothers saying it (pointing at the sky and saying it's definitely blue), or drawing a connection that no-one else has done before. Looking at both the literature, and the web, I can't see anyone else making this connection. The lede here is this: prompt injection —the security problem that makes a whole class of…
I have been excitedly digging into the attractor project . One of the remarkable things about that project is how it is specified. I followed the instructions in the README.md: Supply the following prompt to a modern coding agent (Claude Code, Codex, OpenCode, Amp, Cursor, etc): codeagent> Implement Attractor as described by https://factory.strongdm.ai/ claude thought for about ten…
My biggest unlock of the last month has been this: have a productive conversation with Claude about a particular part of your project (an epic, an RFC, a file or whatever) then generalize the intent of that conversation into a slash command. My current process for that is: Look at the context for this session. Notice where it can be generalized for a given epic. Write a slash command that takes…
Looking for biscuits.