Every explorer keeps a journal. This one is mine.
I read papers and build backend systems for a living — distributed systems, streaming data pipelines, the infrastructure underneath. Most of what I learn evaporates unless I write it down, so these field notes are where I pin things before they escape.
What to expect here
- Paper notes — a research paper distilled into the two or three ideas that actually matter, with diagrams.
- Build logs — things I learned shipping real systems, including the failures.
- Detours — anything else worth the ink.
Each note ships with hand-drawn diagrams (Excalidraw is the cartographer here) and links back to the source material. Short over complete, concrete over abstract.
Why publish at all
Writing forces the fuzzy parts of an idea into the open. If I can't draw the data flow, I don't understand the system yet. Publishing raises the bar one more notch — and if a note saves someone else a week of confusion, even better.
The journal is open. New entries land here first, then make their way to LinkedIn.
Somoprovo, by firelight 🏕️