Posts
All the articles I've posted.
-
Runbook Notes 004: Cloud-Native Graceful Shutdowns
Runbook finally supports graceful shutdowns. In this update: fixing the lost context cancellation from Note 002, using Go’s errgroup to propagate errors, and a neat state-management pattern with first-class functions. No more zombie pods when workflows fail or get cancelled.
-
Runbook Notes 003: New UI, Deadlocks, and AI Overengineering
Goodbye juggling multiple terminals, hello frontend! In this update: workflow visualizations, over-engineered log deduplication, and the self-deadlock that stole an afternoon from me.
-
Runbook Notes 002: Kubernetized
In this note, I dig into what changed when Runbook went Cloud-Native™: YAML parsers betrayed me, Go contexts stopped working, logs got messy, and yet... orchestration got real. Also, I'm pattenting the BORE acronym, and I still don’t have a database.
-
Runbook Notes 001: Designing my Workflow Engine
A design-first case study in software engineering, told through the process of building my workflow engine. This post explores how deferring decisions, starting from minimal constraints, and focusing on orchestration over tooling can lead to more adaptable systems.
-
Everything I hate about Python
A lighthearted, brutally honest rant about Python from the perspective of an old timer who’s dabbled in too many languages to count. From tuple weirdness to PEP8 gripes, this post pokes fun at Python’s quirks while offering a cautionary tale for those new to the language — or just wondering why their loop variables won’t go out of scope.
-
Computers can't store numbers
Knowing a bit of math, and some set theory, and knowing how computers store numbers, I'm making this bold statement: Computers can't store most numbers. And by "most", I mean almost all numbers. So to make it even more engaging and/or enraging: Computers can't store numbers