Why this site exists

Most of what I build gets explained twice — once in a pitch deck, once in a hackathon demo — and then never again. The reasoning disappears and only the result survives.

This is where the reasoning goes. Architecture calls I would defend, ones I got wrong, and the small operational facts that cost a day to learn and take a paragraph to write down.

Nothing here is a tutorial. It is a working notebook that happens to be public.