AI
Why Pod Errors Prompted a Paper Book
Dudfield works on Headlamp, an open source Kubernetes dashboard. People file problems in its Slack channel regularly. The two most common culprits are OIDC and DNS, with OIDC appearing most often. Debugging those failures meant repeating the same steps. He kept notes in text files and paper notebooks while thinking through problems, and eventually started distilling those notes into small books to share with colleagues.
What a Zine Actually Contains
The pod zine runs 16 pages, roughly the size of a hand. Each page covers one error state: ImagePullBackOff, registry outages, authentication failures, DNS issues. Dudfield writes down the two or three commands he reaches for and groups related errors together. The Kubernetes UI already shows tooltips for these errors, but having a physical reference helps when reading a fast-moving terminal. The constraint of 16 small pages forces him to cut every redundant word.
The Physical Format Forces Better Notes
Small pages do the editing work automatically. If three commands exist for a problem, the page fits only one, so you pick the best one. Dudfield compares the process to flash cards for an exam or language study. Writing by hand also shifts thinking away from the editing mode that typing produces. Adding small drawings, stickers, or cut-out photos makes individual pages more memorable than lines of text scrolling past in a log stream.
Folding the 16-Page Book from One Sheet
The whole book comes from one A4 sheet. Fold it in half, crease firmly, fold into four, then fold across again. Three cuts in the middle create a frame. Fold the frame down and squeeze the spine into shape. Straight creases matter most. A practiced person finishes in about 2 minutes and 30 seconds. Dudfield takes about 4 minutes. No glue is needed for the 16-page format, unlike the 18-page version.
Sharing Zines as an Alternative to Runbooks
Sharing is part of the format. Dudfield passed a copy around the room during the talk. For teams working in the same building, handing a zine to a colleague is faster than pointing at a wiki page. Remote teams lose that ease, but the making process itself still has value. He suggests treating zines as a replacement for the runbook or wiki section that nobody reads: draw it instead, write on paper instead, keep it small.
Notable Quotes
mostly it’s oidc René Dudfield · ▶ 01:23
I think the the drawings are even maybe better than um just writing words. René Dudfield · ▶ 07:47
that whole thing took someone practiced about 2 minutes and 30 seconds. It takes me about 4 minutes. I always make mistakes. René Dudfield · ▶ 12:46
Key Takeaways
- A 16-page zine from one A4 sheet needs no glue and folds in under 4 minutes.
- Limiting a page to one command forces better decisions than open-ended runbooks.
- Hand-drawing pod error flows improves recall more than re-reading text notes.
About the Speaker(s)
René Dudfield is a software engineer at Microsoft working on Headlamp, an open source Kubernetes UI. Outside of Kubernetes tooling he builds data audio reactive video synths and maintains Pygame.