Loading…
Writing
Notes on payment systems, device software, transaction uncertainty, platform design, and the emerging role of AI in commerce. I write from the questions that appear in real operating conditions.
A key ceremony is a scripted piece of theatre with real cryptographic consequences. The failure modes are entirely operational.
Every LLM feature has an unbounded cost tail. The controls that prevent a support agent from spending your quarter's budget in an afternoon.
Most postmortem templates get filled in once and then abandoned. The one that stayed had specific properties worth naming.
Layer-2 networks have made stablecoin transfers cheap. The bridge risk that used to concentrate on a few high-profile bridges has changed shape.
The temptation is to log everything. The practical answer is more like ten fields, plus a mechanism for turning on more when you need them.
Every payment API documents idempotency keys. Every payment platform gets some of the details wrong. A pattern guide.
The last mile of a cross-border transaction still fails in predictable ways. A field taxonomy.
A token vault is a small service with an outsized responsibility. Common design mistakes and what to do instead.
Generic engineering interviews miss the specific skills payments platforms need. What to add to the loop.
LLMs are good at turning structured data into readable prose. Reconciliation summary reporting is a well-shaped use case, with narrow guardrails.