How John works with AI
This can only be seen by you, not others. The full coding evidence remains private even when the public report is shared.
How you stack up
- How hard you push6/11you peak at ~6,852 words of pure direction in a single day — the very top sustain ~5,000 every day, week after week; the wildest single days on record push ~10,000
- Hours you put in~7.5h of active building on a typical work day — engaged builders average ~3h, and sustaining 7h+ day after day, week after week, is top-1% territory
- Your AI parallelism8/11you already run parallel at the frontier — 63h of your hours with 2+ agents live vs 108h solo; the Claude Code lead keeps 10–15 going at once, and you work the same way
- Focus quality when you work6/11~28% of your work day is true deep flow (~2h) — the very best hold ~50% of theirs in one unbroken block; yours fragments across parallel sessions, so the gain is directing your attention at one thread for longer
A snapshot of your work
←Hover any day in the grid to see exactly what you worked on that day.
Intensity and Focus
Daily rhythm
Work window 10am–11pm. Afternoon worker — 61% of active time is noon–6pm. Peaks around 5pm, second push at 6pm.
Output
6/10Flow state, day by day
in flow vs supervising, half-hour by half-hour · last 14 daysaxis→You should be in flow state much longer.
You are at 1.1h a day, longest recent run 1.4h.
Flow finds you in: Authoring rubrics and report copy you can judge by eye · Net-new UI you can watch working the same sitting
It never ignites in: Slow-verifiable engine tuning with no quick ground truth · Infra, distribution and media work
The patterns that end it
- 4× — Uninterpretable output, you cannot tell what it means or if it worked
- 22× — Threads drained with nothing queued
- 2× — Bounced or churned design decision
- 2× — Manual ops interruption
▸ show details — how this is calculated
You count as in flow when you are driving two or more agent sessions at once while actually composing. Concretely: in any rolling 15-minute stretch, you touched two or more sessions and spent over 2 of those 15 minutes producing words — typing at ~40 words a minute or dictating at ~130, measured from your real messages (pastes and machine text excluded). This is evaluated every 3 minutes, and brief lulls under 6 minutes inside a run do not break it. Each half-hour block is shaded by how much of it was flow: solid means more than half, the lighter shade means partial (hover for the exact share). Working in a single session, or watching agents run without typing, counts as nudging — real work, not flow.
Where your day leaks
33.9h worked · 9.3h away — for every hour you worked, you were gone 17 minutes.
- Tight days are big days. Your biggest (9.3h Wed) was also your lowest-break (1.9h away).
90 minutes a day is yours: meals, rest, a walk. Past that is drift — 5h a week, 0.8 working days your tightest days prove you can reclaim.
What you worked on, day by day
cell depth = how much of you it got · last 30 days- Diff viewer spread across 9 scattered days — what kept it from one or two dedicated sittings?
- Across the window the product analyzes a person, yet the closest thing to an outside user was a friend asking about the report on 07-09. Did a real external user actually try it this window, or is that still ahead?
- A steady share of the period went to tooling that measures the work rather than the product itself — is that the plan, or did it creep?