Developer builds two-tier logging system to keep a technical blog consistently fed

A software studio founder noticed that despite active development work across multiple projects, nothing was connecting that work to their public blog. The core problem was that writing polished posts after long build sessions felt like a tax, causing skipped days and lost details by the time writing resumed. To fix this, they designed a two-tier system: a quick bullet-point capture log at the end of each session, and a weekly distill step where one post is written from the saved notes. Using Obsidian's Bases feature, they kept per-project logs while maintaining a single auto-generated view across all of them, avoiding a central-versus-local file tradeoff. The capture step was embedded into an existing end-of-session ritual, making consistency a matter of habit rather than willpower.