The last post here went up in March 2020, a guide to keeping monitoring simple. Then the world got interesting, and this site sat frozen while the bio drifted two jobs out of date. If you visited recently, the sidebar and the about page couldn’t even agree on where I worked. I’ll take the hit on that one.
Funny part is, the first post on this blog was about picking Pelican and Netlify specifically to remove the friction that killed my old Hugo site, so I could “gain back that drive to produce content.” Three posts and then six years of silence says the friction was never really the stack. Since that last post I picked up a Principal title at Autodesk, jumped to Lambda to build GPU cloud infrastructure, and moved into engineering management. The writing energy went into RFCs, decision docs, and CNCF work instead, and the blog lost every prioritization battle it entered.
So this is the rebuild. The site now runs on Astro with the AstroPaper theme: dark mode, an RSS feed that’s actually on (I had feeds disabled for eight years and didn’t know until this migration), a talks page, and social cards that unfurl properly. Netlify stays. It’s been quietly deploying this thing since 2018 and has earned its keep. Comments are gone. Disqus wasn’t worth what it cost, and if you want to argue with me about something I wrote, I’m easy to find.
Full disclosure: an AI agent did most of this migration while I made the calls. It audited the old setup, caught that the build was pinned to a Python version Netlify no longer ships (the next deploy would have failed), converted the old posts, and wired up redirects so old links still work. Working with agents like this is a big part of my day job now, and it’s exactly the kind of thing I want to write about here.
What to expect going forward: platform engineering and Kubernetes, CNCF and TAG Infrastructure community work, engineering management, and the occasional personal project. I’m not promising a cadence. I’m promising the next gap won’t be six years.