About

I'm a software engineer. I make these because a diagram is usually the thing that finally made a concept click for me, so I would rather draw it for you than read you the documentation.

What the episodes are

Every episode takes one concept and draws it. Not slides with bullet points, and not a screen recording of somebody reading a manual page. The diagram is built up piece by piece, in the order the idea actually makes sense, and it stays on screen while the explanation happens.

The filter for what belongs here is simple: anything where understanding the mechanism beats memorising the API. That covers backend, frontend, infrastructure and tooling, because the method is the subject, not the topic.

Who they are for

People who can already code, and who were never taught the parts a computer science degree skips. Deployment, infrastructure, and why any of it looks the way it does.

A large share of the audience does not speak English as a first language, so the writing is deliberately plain. Real technical vocabulary stays, because that is what you came for. The English around it gets simplified instead.

How they are made

Every diagram is code, not a drawing. The animation is written in Manim, and the narration is recorded and then aligned to the script character by character, so every visual change lands on the word it belongs to rather than near it.

The articles on this site are not transcripts. Narration is written to be heard once, at speed, and that makes poor reading. Each episode is rewritten as prose, with the diagrams from the episode itself.

The best way to follow along is YouTube.