From a first commit literally titled 'My First Pulumi' (May 2019) to a multi-language, multi-team IaC estate with a self-hosted state backend and hard guardrails (2026): an honest assessment of what Pulumi has been great at, and where it has bitten. Working material, not copy.

Seven Years of Pulumi: The Good and the Bad

The production sequel to the 2022 AWS Batch talk: adopting managed batch compute in 2019, scaling it through array jobs and Step Functions, and the seven-year war against memory, parallelism, and throttling — 181 commits of receipts. Working material, not copy.

Batch Compute in Production: Seven Years of Running the Heavy Stuff Elsewhere

Migrating a ~10-year-old .NET Framework estate to .NET 8 while shipping features the whole time: paired projects compiling the same sources twice, two ORMs kept in lockstep, migrations written for both worlds, a revert that taught pace — and the honest accounting of what 'no big bang' actually costs. Working material, not copy.

The Realities of Porting a Complex .NET Framework Codebase

A repeatable, history-preserving repo-merge technique applied three times across two tech estates (2023–2025): filter-repo subdirectory rewrites, unrelated-histories merges, and cut-point branches as permanent markers. Promoted from the work-initiatives backlog; evidence verified against real history.

Merging Repos Without Losing a Single Commit

Agent-produced survey of ~7 years of day-job and personal work, distilled into candidate posts organised by area and type of change. Every angle is engineering practice, not domain knowledge. Working material, not copy.

Work Initiatives → Blog Posts: The Candidate Backlog (2019–2026)

The series hub for the revival story. All four AI-drafted posts are ported into this workbench; resurrect part by part, then restore the series entry.

Blog Revival 2026 (series)

Ported from data/blog per the authorship policy: the body below is an AI-generated draft, kept as reference material. Resurrect by verifying the facts and rewriting the prose, then promote back to a post.

Reviving My Blog After 3 Years: A Complete Transformation

Discovering AI-Assisted Development

Upgrading Dependencies and Tools

Design System Implementation

The workspace/brain-repo article. A full agent draft exists; structure and accuracy reviewed. Below: the gaps to fill, structural moves to try, and experiments to run before the human rewrite pass.

The Virtual Monorepo: Giving Coding Agents One World to Reason About

The virtual-monorepo article is about how an agent reasons about the world. This companion is about the layer underneath: the workspace as the place a machine gets provisioned — a versioned dev-environment setup, editor integration generated from the same source, and a clear home for org-specific tooling (live here, or vendored in via a package feed).