The films
Watch the work.
11 films play on this page. Every one covers a system that is built and running, and in most of them the platform that built it is doing the narrating. Nothing here is a mockup.
Nothing here is rendered and withheld. Every film that exists is on this page and plays.
Shorter than all of this: 10 clips, 6:58 total, on the start page.
-
StellarView itself
The demo is not the system
Eighty three architecture drawings, for the forty one phases of five builds, every one drawn from a plan before the code existed. The film spends most of two minutes on what came out before it stops to name the product. The film in article one.
-
StellarView itself
The Unboxing
A container starting cold and running every phase of the process in order. Twelve phases, seventy work units, two hundred and ten questions it refuses to answer, and four seconds from one command to a running system. The film in article two.
-
StellarView itself
Where are all the apps?
One job walked from a client document to forty six of forty six issues on a customer’s own board, without cutting away. The film in article three.
-
A brownfield migration
The foundation is already there
One estate read out of its own repository and placed on five rings, with no map for it to be drawn from. Laravel 5.2 and Angular 1.5.8 — the newest thing in that toolchain shipped in 2016. A parallel week, and a defect still open at the end. The film in article four.
-
StellarView itself
What it refuses
Rejected, skipped, stopped — three failure modes on one card. One hundred and eighteen prompt templates you can open and change. A publish destination that refuses itself in its own words, and half a capability that does not exist. The film in article five.
-
StellarView itself
Who runs it
A procurement interview answered against running screens. What it is wired to and what it is not, pull request forty seven with its safety case written into it, and a support queue published without tidying it first. The film in article six.
-
TigeRDS — database command instrument
The senior DBA reflex, written down
Pointed at a real AWS account, read only. It finds 31 database resources and 25 with no automated backup or point-in-time recovery. Asked what they cost, it refuses to fabricate the number, because the Cost and Usage Report is not set up.
-
Youvocate — be your own health advocate
The founder's case
The record that gave rise to the platform. This is not a demonstration and not a scenario: it is the founder’s own case, and it is the reason Youvocate exists. Nothing in it was constructed to make a point.
-
Youvocate — be your own health advocate
The Joneses, the teaching demo
The demo family the product is taught with. The Joneses are fabricated and PHI-safe, and their documents are built from a spec against real code systems, so the ingest is exercised the way a real packet would exercise it. A $52,800 balance bill reaches an estate, the insurer had already denied the duplicate as the hospital’s liability, and the app finds $30,600 that is not owed.
-
SolarScore — field sales and homeowner advocacy
The method, and the software built from it
A door-to-door operator described his trade precisely enough that the factory could build it. The training curriculum and the platform turn out to be the same five moves, written twice — canvassing, rooftop analysis, and advocacy that points at the homeowner as hard as it points at the rep.
-
Gravitas Technology — Cicero member platform
The member portal, put through sea trials
The portal booted against a real backend, and the platform that built it goes through the panels one at a time.
Next
The case, in order →