NIDC 2026 · Room 1B

Getting Shit Done
in Two Worlds

Hello

Stephen
McCullough

  • 30 years shipping software
  • By day principal engineer, Whitespace
  • By night founder, SkillfulGorilla
  • Writes swm.cc
QR code: swm.cc/writing/nidc-takeaway-recipesslides, controls
and the essays
behind this talk

Where this is going

  1. 01The factoryWhat I built to run agents at night, and what runs them now
  2. 02Where the time wentOne change, timed from start to done, in both worlds
  3. 03The modelTwo questions for every change, and six controls that follow
  4. 04Buy undoThe cheapest governance there is
  5. 05What a team is for nowWhat's left for people to do
  6. 06Ask me afterNo Q&A. Find me in person instead

By day

Ten engineers.
Sovereign AI.
Real governance.

Sign-offs on
the sign-offs.

By night

One engineer.
Monoliths.
Barely any of that.

“Ah, fuck it,
it'll be grand.”

By night, from my git log

A quarter of a million
lines changed this year.
After midnight, 68% are
co-authored by an agent.

Before midnight, I'm an engineer.

After midnight,
middle management.

Two shifts.
Same year.

The job didn't speed up.
It changed.

I promised a
stripped-down factory
for the governed team.

It doesn't
exist.

Not the factory.
Where the human stands.

01

I built a factory.
Then I killed it.

Hello world.
A blog.
A web server.
A software factory.

My software factory

thrawn

Plan with one model. Build with many.
One worktree each.

03:15

the morning it worked

And it died
anyway.

QR code: swm.cc/writing/the-platform-ate-my-roadmapthe essay:
The Platform
Ate My Roadmap

plan.md

What replaced it

The planone markdown file, reviewed before anything runs
→
The crewthe plan fans out: one agent, one worktree
→
The control roomevery agent, every repo, one screen

Both laptops. Same repo. Only the repo list changes.

What I kept

One thing.
The code gate.

Nothing ships until a human types the code.

The gate moved to
where accountability
already sat.

02

Where the
time went

One governed change, from start to done

One governed change, from start to done

buildwaiting for a human

This talk is about
the grey.

Most solo work

Under
a day

The governed client

4 days

A team of ten and a team of one
learned the same lessons.

Whitespace

Spec-level review
Docs written for agents
Task-sized tickets

My factory

Spec first, in the repo
Context files per repo
A plan that fans out

The ones I don't like

Whitespace breaks far less than I do.
1 in 6 of my sessions get binned.
Review time is up in both worlds.

03

The model

You know
one-way doors.

Building is nearly free.
Undo is the cost.

Four gates

Easy to undo
Hard to undo
Cheap if wrong
?
?
Costly if wrong
?
?

Four gates

Easy to undo
Hard to undo
Cheap if wrong
Let it runtests and an overnight agent sign it off
?
Costly if wrong
?
?
Whitespace a nightly test run signs it offMe an overnight agent signs it off

Four gates

Easy to undo
Hard to undo
Cheap if wrong
Let it runtests and an overnight agent sign it off
Review the plannot the diff. Agree the spec before the agent starts
Costly if wrong
?
?
Whitespace migrations, changes to the graphMe migrations

Four gates

Easy to undo
Hard to undo
Cheap if wrong
Let it runtests and an overnight agent sign it off
Review the plannot the diff. Agree the spec before the agent starts
Costly if wrong
Ship it, then watchbehind a flag, fast rollback, a human looks after release
?
Whitespace QA sign-off, design QAMe me

Four gates

Easy to undo
Hard to undo
Cheap if wrong
Let it runtests and an overnight agent sign it off
Review the plannot the diff. Agree the spec before the agent starts
Costly if wrong
Ship it, then watchbehind a flag, fast rollback, a human looks after release
Put a human in the waynamed sign-off before release, every time
Whitespace QA, then product, then the customerMe the client

The most irreversible change
in this talk isn't sovereign AI.

A bug that emails the
wrong death notice
to a whole town
can't be unsent.

Stakes don't come from
team size.

Four gates

Easy to undo
Hard to undo
Cheap if wrong
Let it run
Review the plan
Costly if wrong
Ship it, then watchboth worlds still gate this before release
Put a human in the way

I didn't strip the factory down.
I moved the gate.

CONTROL 1 · CORRECT

An autonomy budget

Gate
Let it run. Cheap if wrong, easy to undo
You need
A revert count per repo, per quadrant
Do
Agents merge alone while reverts stay under budget. Blow it, and the work moves up a gate.
CONTROL 2 · PREVENT

The pre-mortem agent

Gate
Review the plan. Cheap if wrong, hard to undo
You need
A plan.md, and a second agent with no stake in it
Do
Tell it: “This shipped and caused an incident. Write the post-mortem.” Fix the plan. Then a human reviews.
CONTROL 3 · DETECT

The shadow run

Gate
Ship it, then watch. Costly if wrong, easy to undo
You need
The old path, the new path, and a diff of their outputs
Do
Run the agent's new code beside the old in production. Flip only when the diff is clean.
CONTROL 4 · PREVENT

Separation of duties, for agents

Gate
Put a human in the way. Costly if wrong, hard to undo
Author
One agent writes the code
Tester
Another writes the tests, from the spec. It never sees the code.
Reviewer
A third reviews. A hook enforces it. A human signs last.

An agent can do everything
except be accountable.

CONTROL 5 · DETECT

The quadrant as code

Gate
All four. This is the 2×2 as infrastructure.
You need
A commit trailer, a hook, a CI check
Do
Every plan task and commit carries Quadrant:. CI checks it went through its gate.

Control 5, for real

Make Active Storage migration idempotent

Quadrant: cheap-irreversible
Gate: plan-reviewed
Co-Authored-By: Claude <noreply@anthropic.com>
$ git log --grep='Quadrant: costly-irreversible' \
    --format='%h %s %(trailers:key=Gate)'

Same thing.
Minus four meetings.

Guardrail,
or expensive fear?

The nodding dog
of security.

Where the model breaks

A thousand undoable changes
add up to an architecture
nobody can undo.

The 2×2 governs changes.
Somebody still has to
govern the shape.

Govern the undo,
not the headcount.

04

Buy undo

The cheapest governance
is an undo button.

⌘Z
No steering committee.

catch · after 18 Jan

class CreateActiveStorageTables < ActiveRecord::Migration[7.0]
  def change
+   return if table_exists?(:active_storage_blobs)
    # ...

One line. A one-way door became two-way.

CONTROL 6 · PREVENT

Turn your reviewers into standards

Gate
Every gate with a review in it
Took
50 real review comments, 15 merge requests
Made
A 244-line standards doc
Do
The agent reviewer gets it verbatim, and cites the section in every objection.

Generic review finds
generic things.

Hello world. A blog. A web server.
How do juniors learn now?

05

What a team
is for now

Can one engineer run
the work of a team?
Yes. Mostly.

A team holds what
can't be undone.

Same change, governed by the undo

Let it run
Review the plan
Ship it, then watch
Human in the way

A team of ten. A team of one.
Same AI. Same factory.
Same answer.

Govern the undo,
not the headcount.

QR code: swm.cc/writing/nidc-takeaway-recipesthe controls

Photo credits