The weekly Loom: selection, script, distribution

The posts on this site compound and the daily logs compound, but the one surface that hasn't been compounding is video — and video is the surface that recruiters and hiring managers actually watch before they make the call.

One Loom a week. Five minutes or less. Recorded on the laptop, embedded on the post it covers, shared once on the distribution channels. No editing. No production. The workflow has three steps: select, script, distribute. Each one has a rule.

Selection

The topic comes from the graph, not from a content calendar.

Every post on this site is a node in Neo4j. Every post has tags, a publish date, and relationships to the projects it touches. The selection query: which of the last five posts has no Loom attached and has the highest keyword intersection with the Hunt pipeline's active job descriptions? That's a graph traversal — post tags matched against the skills the market is asking for right now.

If the query returns nothing interesting, the fallback is simpler: the most recent post I'm proud of. Pride is a signal. If I wouldn't walk someone through it on a call, it's not worth a Loom.

The anti-pattern: a content calendar that schedules topics weeks ahead. By the time the recording date arrives, the topic is stale and the energy is gone. Selection should happen the morning of, from live context.

Script

Not a script. A seed and three bullets.

The seed is one sentence — the same content seed I'd give the drafter pipeline. "Why I picked Neo4j over a vector store." The three bullets are the points I want to hit — not word-for-word, not a teleprompter, just anchors so the recording doesn't drift.

The format: screen share with camera in the corner. Show the actual code, the actual graph, the actual terminal. Five minutes means one idea, demonstrated, with an opinion at the end. No intro music. No "hey guys." No subscribe prompt. The viewer is a hiring manager skimming at 1.5x — every second of filler is a second they skip.

The recording tool is Loom's desktop app. One take. If I stumble, I keep going. If the stumble is bad enough to restart, I restart — but the bar for restarting is high. Imperfect and shipped beats polished and stuck in drafts.

Distribution

Three surfaces, in order.

The post itself. Every Loom embeds on the post it covers, at the top below the lede. The embed is a <figure> with the Loom iframe and a text fallback. The post becomes the long-form companion to the video. Someone who finds the video first lands on the post. Someone who finds the post first gets the video.

The project page. Each project on builddaily.io has a page. A Loom that covers a project's technical decision gets linked from the project page. Over time, the project page accumulates a video walkthrough of every major decision — a richer surface than text alone.

Social, once. One share on X, one on LinkedIn. No drip campaign, no repost schedule, no "in case you missed it." The posts compound through search. The Looms compound through the post embeds. Social is the notification, not the distribution.

The bar

The Loom earned its slot if one of these is true within 30 days:

• A recruiter or prospect references it in a conversation.
• The post it's embedded on gets measurably more engagement than comparable posts without video.
• I rewatch it and learn something about how I explain things that improves the next one.

The third one is the real signal — video is a mirror, and the first few recordings will be rough while the tenth one will be noticeably better. The improvement is the flywheel, not the view count.