Category: Developer Notes

I had a demo video with no narration and a stack of AI tools that could hand me a working script in about the time it takes to make coffee. I used them. I’m not going to pretend otherwise, and I’m not going to apologize for it either — that would be its own kind of dishonesty, and I’ve got no patience left for either the “AI wrote my whole app” victory laps or the “real programmers don’t need that” gatekeeping. Both are posturing. Neither describes how the work actually got done.

You’ve got a video with no narration and a script you want timed to specific moments on screen. Here’s the whole path from nothing to a finished, muxed file — one terminal, zero paid tools.

Each step below is short on purpose, so the overall shape of the job stays easy to follow start to finish. If a step has a More info toggle under it, that’s where the deeper explanation lives — why the command is shaped the way it is, what the flags actually do, and the couple of gotchas that’ll cost you real time if you don’t know they exist. You don’t need to open any of them to finish the tutorial. Open them if you want to actually understand the tools instead of just running them.

The mic always found its way to me. At every family gathering, every night out with friends, the videoke remote would get passed around — and eventually someone would cue up one of “my” songs and hold out the microphone like a dare. I loved those songs. I still do. I knew every word, every pause, every place the singer leaned in. There was just one problem: the song was written for a voice higher than mine. The original key would climb somewhere I couldn’t follow. I’d start strong, feel good through the verse, and then reach that one big note — the one the whole song builds toward — and my voice would crack, thin out, or just quietly give up. Every time. For years I thought it meant I couldn’t sing. Eventually I realized it wasn’t me. It was the key. The song wasn’t too hard — it

You’ve been deep in a Claude Code session for an hour, you close the terminal, and twenty minutes later you need to get back into that exact conversation. So you dig through claude –resume history, squint at a list of session IDs with no context, and hope you pick the right one. It’s a small tax, but it’s one you pay every single day.

Here’s the fix: a two-line hook that writes the exact resume command to a file in your project directory the moment your session ends — whether you typed /exit or just let it wrap up naturally.