codegen
working with an agent when you define a very clear set of requirements, and when you're winging it, are completely different experiences. the latter feels so much worse, in terms of the quality for what you end up with.
I think people who say that using ai for code (or in general) makes you less able to think for yourself are just telling on themselves re what they do when given access to intelligence and knowledge on tap.
I enjoy understanding things, especially on a high level, and find it important if I’m steering a project. When Claude fixes a non trivial bug, I almost always ask it to explain what the problem was to me. And by keeping on top of things I’m able to help it when it gets stuck a lot better too (especially given the non overlapping information and degrees of freedom I have access to).
I enjoy understanding things, especially on a high level, and find it important if I’m steering a project. When Claude fixes a non trivial bug, I almost always ask it to explain what the problem was to me. And by keeping on top of things I’m able to help it when it gets stuck a lot better too (especially given the non overlapping information and degrees of freedom I have access to).


How to be more ambitious: A tutorial for humans with models
How to be more ambitious: A tutorial for humans with models
I work on Claude. It’s an interesting experience: Every day I learn about yet another feat accomplished with or by Claude that I hadn’t considered, didn’t think possible, or simply lacked the curiosity and time to try. This month, it may have helped discover a new planet,
i tried opus 5.5. for 15 years my bio has said "artist working with code". today i changed it to "artist".
i'm not "working with code" anymore. i'm thinking in systems, and writing in natural language. i've only been programming for 25 years. any code i write is going to be vastly inferior to a frontier model.
i also have this sense that the generating code is becoming an inseparable feature of daily life. it's so obvious it's not even worth mentioning. "artist working with code" is like saying "artist working with physical matter".
software engineering with LLMs is sort of like diffusion
refining the program you want out of a noisy version
refining the program you want out of a noisy version
ngl, doing software development in the age of (good) LLMs feels far more like caring for a bonsai tree than doing engineering
like, the codebase grows and changes in response to requirements, and your role is mostly just trying to keep it pretty and small
People who direct teams of software developers have been "vibe coding" for decades. The only novel thing is that the rest of us can do it now.
my entire job with these coding agents is down to:
- whittling handholds so they are obvious to humans and agents
- refining sides so they dont give splinters
- putting knives away so nobody hurts themselves
- reducing epicycles
and the only way to scale this has been with tooling that scales involving me
- whittling handholds so they are obvious to humans and agents
- refining sides so they dont give splinters
- putting knives away so nobody hurts themselves
- reducing epicycles
and the only way to scale this has been with tooling that scales involving me
Replying to
@ankrgyl a related lens that I've been enjoying: LLM codegen = JIT compilation in trad PL.
An LLM is essentially a dynamic interpreter for English - flexible and slow. On the go it can choose to "compile" deterministic code for hot paths: faster but more rigid
An LLM is essentially a dynamic interpreter for English - flexible and slow. On the go it can choose to "compile" deterministic code for hot paths: faster but more rigid
Today, right now, we are effectively at the point where sufficiently describing a computer program is equivalent to source code for that computer program.
I'm not up on this, we might be at a point where describing a small convex object is equivalent to having manufacturing specs for that object.
Quotes @elucidating.extradimensional.spaceI'm not up on this, we might be at a point where describing a small convex object is equivalent to having manufacturing specs for that object.
New blog post: "A sufficiently detailed spec is code"
I wrote this because I was tired of people claiming that the future of agentic coding is thoughtful specification work. As I show in the post, the reality devolves into slop pseudocode
haskellforall.com/2026/03/a-suff…
I wrote this because I was tired of people claiming that the future of agentic coding is thoughtful specification work. As I show in the post, the reality devolves into slop pseudocode
haskellforall.com/2026/03/a-suff…