DEVRELCON NYC · JULY 22, 2026
What Makes Developers Actually Ship?
Removing friction in the first mile
Ojus Save
Troy to Ithaca.
565 nautical miles.
One modern sailor's estimate.
It took Odysseus ten years.
Some of his men were eaten.
Some were turned into pigs.
One fell off a roof.
At one point, Ithaca was in sight.
Then the crew opened the Bag of Winds.
He left Troy with 12 ships and roughly 600 people.
Only Odysseus reached Ithaca. He arrived as a beggar.
Developers don't arrive to complete your onboarding.
They arrive to build something.
Try to reach the first usable result.
WORKSHOP EXERCISE The QR opens FakeGPT. Give it one small thing you want to build, then follow the prompts.
LIVE DASHBOARD EMBEDS HERE
set CONFIG.dashboardUrl
TIME
Stop where you are.
RESULTS VIEW IS NOT CONNECTED
Stage navigation skips this slide until the event results URL is added
TRACKER SCOPE
This is what the tracker recorded.
Recorded
- Named step and timestamp
- Retry and bounded machine error
- Terminal completion
Not recorded
- Fake account or card values
- Form contents or page text
MY RESEARCH · DEVELOPER JOURNEY ATLAS
I examined developer platforms.
one selected developer goal and one official documented route per platform
One record covers one selected route, not the whole company journey. This is documentation research, not observed developer behavior.
WHAT I FOUND · FIRST-SUCCESS CLARITY
Only explicitly named first success.
explicitly named the first-success milestone
showed a terminal result without naming the milestone
A demonstrated endpoint is not the same as a clearly named milestone. This finding describes documentation, not completion behavior.
WHAT I FOUND · ROUTE CONDITIONS
I documented gates. The median route had .
included at least one credential requirement
included at least one documented choice
included at least one documented wait
A gate is a documented requirement or transition. These counts overlap and do not prove difficulty, drop-off, or cause.
A SEPARATE DATASET · POSSIBLE EXPLANATIONS
I cataloged possible blockers. None is a diagnosis.
plausible blocker hypotheses
universal
platform-specific
EIGHT EXAMPLES FROM THE CATALOG
These are hypotheses I would test, not assume.
Account
and identity
Work email required
Verification delayed, filtered, or expired
Billing
and access
Card before evaluation
Cannot create the required key, certificate, service account, or OAuth app
Setup
and recovery
Prerequisites appear too late
No reset, undo, rollback, or clean restart
Errors
and waits
Generic error
Provisioning, build, deploy, indexing, or model loading takes longer than expected
DEVELOPER JOURNEY ATLAS · OPEN SOURCE
I built Atlas for peers improving developer platforms.
- Find your platform or browse a peer cohort.
- Inspect prerequisites, actions, gates, and the first-success boundary.
- Correct or contribute what is missing through a pull request.
LIVE ATLAS EMBEDS HERE
set CONFIG.atlasUrl
FROM DOCUMENTED ROUTE TO OBSERVABLE POSITIONS
Atlas maps the route. Calibrate observes positions in yours.
01
Atlas
Provides a documented route hypothesis.
02
Calibrate
Records named positions and bounded route events.
03
Human debrief
Supplies what the developer expected and tried.
Add Calibrate to one route.
npm install usecalibrate@0.1.3npx usecalibrate plan --dir . \
--route /signup=account \
--route /welcome=success:shipped \
--out calibrate.plan.jsonnpx usecalibrate apply \
--plan calibrate.plan.json --yes
npx usecalibrate verify --dir . --jsonPosition tells you where to ask. It does not tell you why.
RECORDS
- Named route positions and forward or backward movement
- Completion, elapsed time, and bounded machine errors
- Configured copy or paste outcomes and explicit shipped event
NEVER READS
- Form or textarea values and clipboard contents
- DOM text, labels, or placeholders
- Full URLs, query strings, or hashes
TAKE-HOME EXERCISE
Run ten intended users through one route.
- 1Choose one intent and first useful result.
- 2Recruit intended evaluators, including people new to the route.
- 3Give them the outcome, not step-by-step instructions.
- 4Use Calibrate to see where activity changed. Then ask what they expected.
- 5Bring the owner one question, one piece of evidence, and one next check.
OPTIONAL WORKSHOP RESOURCE
Need somewhere to
host the replica?
- 1Scan the QR code.
- 2Continue with GitHub.
- 3Copy the code and redeem it from Render Billing.