Show developers how your product works inside
An interactive article about how your product works inside, with animations that behave the way your product does. It goes on your blog or in your docs, and I cut short clips from it for LinkedIn, X and YouTube.
Why an animation
Developers don't trust a diagram with five boxes and some arrows. They trust something they can poke at. The animation above is from the rate limiter article: two servers share a counter, and a race lets one extra request through. Watch it once and it's clear why the fix matters. A paragraph about atomic operations rarely gets that across.
What you get
- An interactive article about one thing your users get wrong or don't see, ready for your blog or your docs.
- Animations that follow how your product really behaves, with your defaults and your limits. One of your engineers checks every number before it goes out.
- Short clips from the same animations, with captions, sized for LinkedIn and YouTube Shorts.
- Updates when your product changes. A new limit or a new default means I update the animation, not redraw it.
How it goes
- A call about what developers misunderstand about your product, and which moment would clear it up.
- I read your docs and spend an hour with one of your engineers.
- A storyboard on paper first, so the story can still change cheaply.
- I make it, your engineer checks it, and you publish it.
Pricing is per project. We agree on it after the first call, once we both know how many animations the story needs.
Get in touch
Send me a line about your product and what you'd like people to understand about it.