Blog

Hand-drawn, semantic, step-based, course and recording workflows for code videos, compared on one shared fixture with dated sources and a hands-on record.

A one-line bug-fix diff, pasted into Scribe and exported as a real hand-drawn video, tests whether a walkthrough beats a wall of diff lines in review.

A five-line quickstart, drawn by Scribe and exported as a real GIF, is what actually embeds in a GitHub README: no screen recorder, no video host.

A nine-line bubble sort, drawn step by step with Scribe and exported as a real video, tests whether watching comparisons beats reading pseudocode.

A small debounce helper, drawn by Scribe and exported as a real video, is what I tried instead of a webcam or a screen recording to explain it.

The same code fixture in two formats: what a screen recording keeps, what a stroke-by-stroke code walkthrough makes legible, and a rule for choosing.

Script a hand-drawn explainer in three beats: one change in the viewer's head, a pause with a job for each beat, and a preview checked before you publish.

Cut a how-to doc down to the steps a viewer must follow, draw them in order with Scribe, and keep the written page as the source of detail.

Use one whiteboard animation to explain the same loop to a developer and to a learner: a shared code input, two framings and a checked Scribe export.

A six-line helper decided whether Google indexed four homepages, and its pull request went unread. Here is the same change as a 60-second hand-drawn video.