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.
On-call for a team spread across three or more time zones needs different shapes than a co-located team. The patterns that work.
The engineer who is present but disengaged is a specific management problem. What's actually going on, and what a manager can do about it.
Most postmortem templates get filled in once and then abandoned. The one that stayed had specific properties worth naming.
Generic engineering interviews miss the specific skills payments platforms need. What to add to the loop.
"Break up the monolith" is often shorthand for "rewrite the system". A more disciplined approach that ships.
Documentation gets treated as an aftermath. Treating it as a deliverable — with the same discipline as code — changes what the team ships.
Most one-on-ones are status updates. The ones that build the relationship and surface problems have a different shape.
Saying yes is easier in the moment. Learning to say no well is one of the highest-leverage skills for engineering leaders.
A team distributed across three time zones has specific coordination costs. What scales, and what stops scaling.
Some technical decisions should be made by engineers alone. Others need explicit stakeholder input, and getting the line wrong causes friction later.