Writing
Notes on payments, architecture, and engineering leadership.
General lessons and opinions on payments architecture and engineering leadership — the things I would want written down for a team starting the same work. They are not case studies of any one employer's systems.
-
Zero-Downtime Cloud Migrations for Payments Platforms: What to Check Before Cutover
What "zero downtime" has to mean for a payments platform, five categories of risk to map before cutover, and why the rollback gate needs to be written down in advance.
Read article -
Decomposing a Payments Monolith Without Stopping the World
When not to decompose, bounded contexts without dogma, strangler-fig sequencing, the contract-test layer that buys you speed, and the outbox-pattern mistakes to avoid.
Read article -
What "Hands-On Engineering Manager" Actually Means
How I think about splitting a week between management and code, where hands-on time is worth the most, where it backfires, and the question I ask before taking on an engineering task.
Read article -
Idempotency Keys in Payments — Five Mistakes I've Watched Get Shipped
The "obviously correct" implementations that ship duplicate charges anyway. Composite keys, retry windows, state machines, and which layer is the right one.
Read article