For the people who build, own, and operate.

InsanelyGreat

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

Reference Architecture · v0.9.5
Domain-Adaptive Manufacturing
Software that builds and configures itself to the reality of the manufacturer. From a two-person startup to Nestlé or Apple. Standardize the physics, bespoke the experience.
Read the architecture
Methodology · v2.11 · SSD 2.0
Shippable States Development
Ship every day. No exceptions. A pragmatic AI-powered discipline that keeps your software deployable at all times — now one progressively-disclosed surface for newcomer and expert alike.
Learn more
Manifesto
Agile2
The ability to be agile about your agile. Process is a tool, not an identity. If it doesn't increase velocity, change it.
Read the manifesto
The After Effort Project · Course & Software
After Effort
The disciplined use of AI in teaching. A tool helps a student most when it comes after their own effort, not in place of it — the professional-development course, and its software companion, UpwardTeaching.
Explore the project
New in v2.11
Your gate now checks whether you actually followed the method.
For eleven releases the gate verified hygiene — no WIP commits, tests green, frontmatter valid — and not one of the eight rails invariants. The new rails-walked rule closes that: a release that ships a feature with no passing code review now fails the gate, loudly, before you tag it.

It exists because SSD pointed its own epistemic audit at itself and found it had done exactly that — shipped a release unreviewed, with every check green. Running the new rule back across all 25 releases in the library's history turned up that one, and confirmed the other 18 had been done properly by hand. The gap was in checking, not in doing — which is more useful to know, and not the answer the audit had predicted.

Also new: a private artifact store keeps your .ssd/ history version-controlled in a separate private repo — so private mode no longer means your methodology record is untracked files on a single machine.
See what's new

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.