Blog post: https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/
Author: Armin Ronacher. Published March 20, 2026.
Blog post: https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/
Author: Armin Ronacher. Published March 20, 2026.
Blog post: https://haskellforall.com/2026/03/a-sufficiently-detailed-spec-is-code
The post argues that the agentic coding movement's promise — that engineers can simply write specification documents and have AI agents generate working code — is fundamentally flawed. The central claim is captured in the title: if you make a specification precise enough to reliably generate correct code, the specification itself effectively becomes code. There is no shortcut that avoids the hard intellectual work of programming.
Podcast: www.youtube.com/watch?v=kwSVtQ7dziU
This is a comprehensive analysis of the interview with Andrej Karpathy on the "No Priors" podcast, detailing the profound shifts in software engineering driven by AI agents and Autoresearch.
This including key insights, a structured outline, and any critical nuances mentioned.
Most software engineers are using Codex and Claude Code like they are opening a fresh chat window and hiring a new intern every time.
New thread. New prompt. Same repo. Same rediscovery tax.
The main agent has to re-learn the codebase, re-infer the architecture, and re-guess what matters. Then people wonder why results are inconsistent, slow, and fragile.
Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:
A new AI product launches that sparks a market panic. It’s a new initiative, or an agent or something. Whatever it is, I can tell you one thing it can’t do.
Even with the best AI model in the world, the one thing it can’t do is its best work for you.
How do I know? Because the state of frontier models has gotten so advanced that to get the best talents out of any of them, you need different models to work together. The biggest weakness of Claude is that it only coworks with Claude
No one model family can do its best work for you without the talents of others. As models get more powerful, we’re seeing them specialize. The future state of AI is your best work will get done when there are different models working together.
OpenAI just released GPT-5.4 and Codex 5.4, and the early reactions from developers are unusually strong.
Some report that it solved bugs earlier models failed to fix after dozens of prompts. Others describe it refactoring entire codebases in a single run. A few say it has already become their daily driver for coding and knowledge work.
But none of those anecdotes capture the real significance of this release.
| name | orchestrating-swarms |
|---|---|
| description | Master multi-agent orchestration using Claude Code's TeammateTool and Task system. Use when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns. |
Master multi-agent orchestration using Claude Code's TeammateTool and Task system.
This is not a proposal. This documents existing but hidden functionality found in Claude Code v2.1.19 binary, plus speculation on how it could be used.
TeammateTool already exists in Claude Code. We extracted this from the compiled binary at ~/.local/share/claude/versions/2.1.19 using strings analysis. The feature is fully implemented but gated behind feature flags (I9() && qFB()).
A system where the large language model (LLM) serves as the brain, natural language is the programming interface, and tools function as devices.
| Classical OS | Claude Code |
|---|---|
| Kernel | Claude (reasoning engine) |
| Memory | Context-window |
| Shell | Natural language |
| Process spawning | Sub-agents |