My First Time Recording Developer Videos (It Was Actually Fun)

I’ve been an engineer for 20 years. I’ve written code, given talks, written blog posts. But I’d never recorded developer videos.

That changed recently when I started creating product demo videos for Flox. And here’s what surprised me most: it got easier way faster than I expected.

If you’re an engineer who’s thought about making videos but keeps putting it off—this is for you.

Why We Made the Videos

Flox makes reproducible development environments easy. The problem? “Reproducible development environments” doesn’t exactly roll off the tongue. Showing beats telling.

We wanted product demos that actually show what Flox does—real terminal sessions, real workflows, real problems being solved. Marketing awareness, yes, but grounded in actual engineering work.

The goal wasn’t polished corporate video. It was authentic developer content.

The Hard Parts (There Were Several)

Let me be honest about what was difficult:

Scripting and flow. What do you actually say? How do you keep it concise without sounding robotic? I rewrote scripts multiple times before finding a rhythm that felt natural.

Multiple takes. Getting it right means doing it again. And again. My perfectionist brain wanted every take to be perfect. Spoiler: that’s not how this works.

Keeping energy consistent. Take 1 sounds enthusiastic. Take 7 sounds tired. But you need to cut between them. Maintaining consistent energy across multiple takes is harder than it sounds.

First time in a real studio. I flew to Warsaw for a full day of recording at Studio MIS—professional lights, cameras, the works. Walking into that setup as a first-timer was intimidating. But having Joanna Kasprzak-Kajder guiding me through the whole process made all the difference. Her experience with developer content and patience with my learning curve was invaluable.

The combination of all these at once felt overwhelming at first.

The Surprise: It Gets Easier Fast

Here’s what I didn’t expect: by the second or third session, I actually started enjoying it.

The initial awkwardness fades quickly. You find your voice. The technical setup becomes routine. What felt like an insurmountable challenge becomes… kind of fun?

I think engineers avoid video content because it feels too exposed, too different from our comfort zone of code. But the learning curve is shorter than you think.

What I’d Tell Other Engineers

If you’re considering making developer videos, here’s my advice:

Just start. You won’t feel ready. Start anyway. The first video won’t be great. That’s fine. No one’s first video is great.

Embrace imperfect. Done beats perfect. Every time. Ship something. Learn from it. Make the next one better. This is the same iteration cycle we use in code—apply it to content.

Get out of your comfort zone. Yes, it feels weird to be on camera. Yes, you’ll cringe at your own voice. Everyone does. Push through it. The discomfort shrinks with practice.

Keep it short. Developers don’t want to watch 30-minute videos. Say what you need to say and stop. Shorter is almost always better.

Was It Worth It?

Absolutely.

Not just for Flox—for me personally. I learned a new skill. I pushed past a mental barrier I’d built up for years. And I discovered that “content creation” isn’t just for content creators. Engineers can do this too.

Here they are—all eleven of them:

They’re not perfect. But they exist. And that matters more than perfection.

If you’ve been putting off making developer content: stop waiting. The tools are accessible. The learning curve is shorter than you think. And you might actually enjoy it.

I’m an engineer at Flox and founder of NixCon. Currently figuring out developer content one video at a time. Let’s connect.