Andrew Stellman

I take difficult technical topics and make them really easy to understand.

Through my books and courses, I’ve helped people understand coding, project management, Agile development, working with teams, leadership, and process engineering and improvement. Now I’m tackling artificial intelligence.

I’ve written six O’Reilly books with my longtime collaborator, Jennifer Greene, and our books have been translated into more than a dozen languages.

If you want to learn about what I’m working on now, here’s a good starting point: The Accidental Orchestrator. I describe how I used AI to build Octobatch and what I learned along the way.

I’m a New York-based developer, architect, author, and international speaker.

Andrew Stellman speaking at Foo Camp 2026

Foo Camp 2026: “It’s a Feature, Not a Bug.” Watch →

Current project

Learn how LLMs work by being each piece of one.

In this book, you learn how LLMs work by doing each part of a model’s job by hand. You choose the next word from real corpus statistics, set the weights on a neuron, and work through attention calculations. You also build a working model with AI, then run it in PyTorch and export it to Hugging Face.

Explore the book and try the toys →

Now

Books and Reports

Background

Articles on AI-driven development

In my O’Reilly Radar series, I write about how you can work with AI coding agents, check their code, and manage their context. Read all my Radar articles →

  1. The Accidental Orchestrator
    How I started Octobatch to handle unreliable LLM output.
  2. Keep Deterministic Work Deterministic
    Pull deterministic work out of the LLM’s hands. A pipeline went from 31% to 84% passing.
  3. The Toolkit Pattern
    Write documentation for the AI to read: AGENTS.md, CLAUDE.md, and why they work.
  4. AI Is Writing Our Code Faster Than We Can Verify It
    Apply classical quality engineering to AI-generated code: requirements first, then verification.
  5. AI Code Review Only Catches Half of Your Bugs
    Write down what your software must not do. Negative requirements catch the intent bugs structural review misses.
  6. Why Doesn’t Anyone Teach Developers About Context Management?
    Treat an agent’s context the way you treat memory: manage it deliberately.
  7. Your AI Agent Already Forgot Half of What You Told It
    Four techniques: split discovery from documentation, handoff documents, acceptance criteria, spec documents.
  8. When Context Collapses
    Externalize, recognize, rehydrate: save agent state to disk, detect when context has degraded, reload.
  9. So Long and Thanks for All the Context
    Keep the agent’s working context small, with important information near the beginning and end.
  10. My AI Kept Pushing Me to Ship, So I Asked It Why
    Recognize continuation pressure, the bias that keeps nudging you toward the next step.
  11. We Keep Renaming AI Coding. Here’s What I’d Call It.
    Why the name matters, and the case for calling it AI-driven development.

Earlier articles on coding with AI

I adapted my Radar series on the Sens-AI framework into the O’Reilly report Critical Thinking Habits for Coding with AI. The original framework article introduces the habits and links to the rest of the series.

Tools you can run today

An open-source skill that guides AI coding agents through code reviews using quality engineering techniques.

A batch orchestration tool for large-scale LLM processing, with a TUI, Monte Carlo simulation support, and AI-assisted pipeline development. I used AI to write all of its code.

A batch orchestrator for AI coding agents that runs inside your existing agent session. No server, no daemon, no admin rights.

Research

I’m researching how to apply traditional quality engineering to AI-written code. The Quality Playbook is the open-source implementation, and it has found bugs in Google’s Gson and the Linux kernel’s virtio and zram drivers.