one handoff, start to finish

Everything your editor needs to cut the 2.4 release video.

One link instead of a folder and a call: the angle, the commits and recordings it came from, the script before and after review, and the reviewer’s note on what is left to record.

Ipsum Analytics and its Placeholder API are made up.

A Markdown file you can read or forward.

A studio table at night: frame prints and a storyboard notebook, a tablet showing a draft with cited lines highlighted, a laptop showing an edit timeline, and a phone showing the published cut — Fig. 1The desk this replaces: the prints, the storyboard, the draft, the timeline, the published cut.

Ipsum Analytics — the Placeholder API

Approved

Release 2.4 — the export stopped timing out, and the fix deleted more than it added

01 — The angle

The angle, and why it won

Customers have been reporting export timeouts for two years. The fix turned out to be streaming rows straight to the response instead of building the whole file in memory first. Open on the support thread. Close on the two runs side by side.

Why this storyChosen over the new dashboard because the timeout thread has 38 replies and is the most answered question in the support inbox this quarter. The change also sits in one subsystem, so four minutes can cover it in depth.

02 — What it’s built from

What it’s built from

Each item says why it was picked. In your own drafts, a matched clip or timestamp is a lead until you have watched it.

Support thread — “CSV export fails on anything over a million rows”
38 replies · reopened four times
Why it’s hereThe cold open: customers describing the problem in their own words.
7be41d0 — stream export rows instead of buffering the file
+612 −840 across services/export
Why it’s hereThe core of the piece. The fix removes more lines than it adds.
export-run-2.3.mov — 2.4 million rows on the old code
0:38 · screen recording
Why it’s hereThe first half of the pair below. The request gives up at sixty seconds.
notes/streaming-tradeoffs.md
engineering note, 900 words
Why it’s hereCarries the cost: the progress bar can no longer show a total.

03 — The run

Two runs of the same export

One export, two releases. Your editor opens both runs and sees the difference.

Fig. 2ExampleBefore — export-run-2.3.mov. 2.4 million rows on the old code. The request gives up after sixty seconds.

no clip yet

Fig. 3ExampleAfter — no clip yet. The same export on 2.4, finishing in 41 seconds, drawn from the engineering note. No clip attached yet; the reviewer’s note asks for the run.

04 — The script

The script — as written, and as you left it

Both versions are kept, and the difference between them is recorded as an editorial decision.

As generated

Two years ago somebody asked why a CSV export dies at a million rows. This release is about why the fix removed code instead of adding workers.

As edited · approved

Two years ago somebody asked why our CSV export dies at a million rows. We added workers. We added a queue. We paid for a bigger box. This release is about the week we stopped adding things and deleted the part that was holding the whole file in memory.

What it took from thatThe reviewer kept the opening question and added the three short sentences before the turn. Recorded as an editorial decision: this company opens by admitting what it tried first. The next draft starts from that.

05 — Material

Material, and the reviewer’s note

The recordings and files attached to the script, and the reviewer’s note on what is still to record. Your editor gets both in the same link.

Already recorded

export-run-2.3.mov — screen recording of the failing export, 0:38
memory-profile.png — peak memory per export, 3.1 GB down to 38 MB
support-thread.png — the original report, names removed

Reviewer’s note: still to record

Written by the reviewer. A beat with no clip stays in the script, empty.

Screen recording: the same export on 2.4 — Same terminal size and same file as the 2.3 run, so the two cut together cleanly.
Talking head: 20–30s on what you gave up — One take, said plainly: “the progress bar can no longer show you a total.”

06 — The ask

What the editor is being asked for

Cut a 3–4 minute release video. The two export runs are the spine, and the script is approved as edited. The reviewer’s note above lists the two things still to record, with how to frame each.

Mon 09:14GeneratedDraft built from 4 evidence items.
Mon 09:40In reviewSent to reviewer (editor seat).
Mon 16:02Changes requested“The opening skips the two years we spent buying hardware. Say that part.”
Tue 08:31In reviewRevised opening; tone note recorded.
Tue 11:47ApprovedHandoff generated for the editor.

In your project, corrections you repeat guide later drafts. They do not guarantee a better one.

Yours would be built from what you shipped.

Connect the repo, the recordings folder, or the account you post from, and the first one starts from what you shipped last week.

Get started