For the people who build, own, and operate.

InsanelyGreat

Enabling people striving to make their own dent in the Universe.

Methodology · SSD 3.0
Shippable States Development
The model proposes. The harness enforces. You still ship every day. Executable gates, grants that live outside the repo, and a ship command only a human runs.
Learn more →
Architecture · Manifesto · Philosophy · Approach
Projects
Domain-Adaptive Manufacturing, Agile², True As Of, and After Effort.
See the projects →
Telemetry
Instrumenting the Organization
Most companies measure activity. Flow is the thing that pays. How to instrument an organization the way you would instrument a factory, and what AI changes about the instrument.
Read it →
Engage · Independent consulting
Technology Engagements
Innovation and technology refresh for software companies, media companies, and teams securing AI/ML systems. Thirty years of shipping, from NeXT and Apple to Snowcap Compute.
How engagements work →
SSD 3.0 · why this matters
The model proposes. The harness enforces.
Agentic coding moved from the prompt to the harness. SSD 2.x asked the model to follow the rail. SSD 3.0 runs the rail: executable gates, grants that live outside the repo, one use, bound to a snapshot, and a ship command only a human runs. Doctor and resume keep the work after an interruption. The eval harness names what it proved.

Live model runs, the five-user pilot, and an in-session load of AGENTS.md are NOT_RUN. A row that did not run is not a pass. True as of 12 October 2026, skills main at c6dd481: pull request #58 is on main, untagged, with no GitHub release. The boundary is what’s in 3.0, and what is not. A claim carries a date: True As Of.
Why SSD 3.0 Try the tutorial

Essays — from teams of one to organizations of thousands

Opinionated articles on how work actually moves — at whatever scale you are working at.

At organizational scale

Telemetry

Instrumenting the Organization

Most companies measure activity. Flow is the thing that pays. How to instrument an organization the way you would instrument a factory — and what AI changes about the instrument.

 Reference Architecture

Domain-Adaptive Manufacturing

Software that builds and configures itself to the reality of the manufacturer — from a two-person startup to Nestlé or Apple.

For solo developers and small teams

Manifesto

The Solo Developer's Engineering Manifesto

Engineering practice for the developer who is also the PM, QA, DevOps, and support team.

 Comparison

Methodologies for Small Teams: An Honest Comparison

Scrum, Kanban, Shape Up, XP, and SSD — for teams of 1–5.

 Critique

Why Standard Scrum Fails Small Teams

Scrum was designed for 5–9. Below 3, the ceremony costs more than it delivers.

 Quality

Code Quality Without a QA Team: The Ratchet Principle

Encode quality in CI. The teeth of the ratchet are tests, types, and lint rules.

 Releases

How Small Teams Should Think About Releases

Decouple deploy from release. Make the release a flag flip and a changelog entry.

 Simplification

The Simplest Engineering Lifecycle That Actually Works

Most lifecycle complexity is scar tissue from past deployment trauma.

On claims

Philosophy · v0.1

True As Of

Every claim to truth we can actually hold carries a timestamp. State the regime, the tolerance, the test, and the date.

 Commentary

Fooling Yourself

Feynman’s 1974 address, with notes on what it asks of people who measure their own work.