Compass Navigation Streamline Icon: https://streamlinehq.com
applied cartography

Screen record more

One of the things I miss most about working in an office is osmosis: the ability to absorb information from coworkers purely by peering over their shoulder for five minutes and seeing how they did their work. This is how I learned about using a debugger. About NeoVim. About a dozen other small ergonomic tricks that I've since internalized to the point I can't remember a time without them.

The other thing I miss — and this one is more niche — is rubber ducking. The term is a bit of a meme at this point, but if you haven't encountered it: to rubber duck a problem is to walk through it out loud, explaining it to a rubber duck as if the duck were an actual person. The trick, of course, is that the act of articulating the problem is itself the thing that surfaces the solution. In the office version, the duck is a real person who passively observes and provides no input.

The good news — and something I forget, and am writing this post primarily as a reminder to myself — is that we have the technology to do both of these things, albeit without the ambience.

It's called taking a screen recording of yourself.


It doesn't have to be while doing anything in particular. I've both sent and watched screen recordings of me literally just triaging Linear, going through support escalations, and implementing a new bulk action — to give you a sense of the banality. They can be long. They should ideally be completely unfiltered and unedited.

The only real caveat is that you should narrate while recording: talk about what's on your mind and why you're doing the things you're doing. But you should not change your behavior. No tidying up the desktop, no rehearsing the click path, no skipping the part where you fumble through a menu for thirty seconds because you can't remember where the setting lives. The fumbling is the point.

It sounds obvious, I know. But if you haven't done it a lot, it is tremendously beneficial as a way to share tacit knowledge — the kind of knowledge that nobody writes documentation for because nobody realizes they have it.


About the Author

I'm Justin Duke — a software engineer, writer, and founder. I currently work as the CEO of Buttondown, the best way to start and grow your newsletter, and as a partner at Third South Capital.

Colophon

You can view a markdown version of this post here.