Tokens/sec is the easiest optimisation https://lnkd.in/gVZarwKM

You are at the keyboard with your coding agent building the most important thing as fast and as well as you can. But the coding agent is slow, and you want to be as productive as possible, so you do the things you know how to do. Get the agent running overnight (effort to enable increased autonomy), parallelise (effort to enable separation of work, integration of separate git trees). This actually doesn’t help with your goal of getting the most important thing done as fast and as well as you can. It lengthens feedback loops, increases cognitive overhead – all the old cycle time vs throughput arguments apply.

So what can you actually do to achieve your goal? More tokens/sec! Just keep doing what you’re doing, but faster. If it’s fast enough for you to stay directly engaged with your highest priority work at your preferred level of abstraction, you will find it very satisfying.

I don’t want you to think I’m for or against Ralph loops etc. I’m exploring and learning like everybody. But I think we are missing the easiest optimisation, and I do worry that we are introducing unnecessary complexity as workarounds instead.

So now that I can finally get more tokens/sec (Cerebras team, help me!) I’ll go back from Claude Code CLI to Codex CLI for a little bit, and lean back into ADDD (Agentic Dictator Driven Development) and see how I like it at this speed.

Soon I’ll try to talk about _refinement_ more. We are all very focused on initial dev which is very exciting at the moment, but the euphoria of a quick AI build can sometimes be short-lived.