Process without bureaucracy: keeping a smaller set of rules
Process earns its keep when it prevents a specific, recurring failure. Anything else is overhead wearing a process costume.
Blog
Notes on infrastructure, engineering, and process.
Choosing a database for the next five years, not the next five months
Database choice is one of the few decisions that gets meaningfully harder to reverse over time. It deserves slower thinking.
The cost of technical debt nobody tracks
Technical debt is usually discussed as a metaphor. Treated as a ledger instead, it becomes something a team can actually manage.
What a security review should actually cover
A checklist is a starting point, not a security posture. The reviews that hold up under pressure look past the checklist.
Migrating legacy systems without a full rewrite
A full rewrite is rarely the fastest path to a modern system. The strangler pattern, applied patiently, usually is.
Evaluating infrastructure resilience before it gets tested for you
Most teams find the weak point in their infrastructure during an incident. A structured resilience review finds it earlier, and cheaper.