Journey
A chronological log of engineering moments — daily notes, project updates, debugging insights, and small experiments.
What is Journey? Short, dated entries that don't fit a long-form article — what I learned, broke, fixed, or shipped on a given day. For deeper architecture notes and articles, see the blog.
A social pipeline that published one Reel a day and nothing else, because per-format quotas were ceilings and nothing was asking for the other formats.
My morning briefing started failing. Ollama was up and returned HTTP 500, because a 21-second image render was still holding 6.6 GB of VRAM hours later.
Five high-severity alerts from my own monitoring. All five were the same defect: a record that names something being read as an observation of a property it never measured.
My homelab brain noticed problems and did nothing about them. Closing the loop meant four human gates and an executor whose defining feature is that it stops at a draft PR.
Every morning my homelab turns its own event log into a written summary and posts it to my notes app. The interesting part is what it does when it cannot tell whether it already did.
Two Pi-holes, a floating IP, and a major-version upgrade on the box that resolves everything in the house. The trick is that the safe procedure and the risky procedure look identical from the outside.
The meta post. Stood up this blog, wrote this from the couch on my phone. Quick Note works.
Polly's SSML <mark> tags emit timing events over the stream. Useful for synchronizing on-screen captions to voice playback.
Integration test green, staging green, prod failing for 1% of callers. The bug was in a place I would never have guessed.