Writing
Short engineering write-ups from the systems I've shipped — each one walks a single trade-off: the problem, the naive approach and why it fails, the decision, and how it was verified.
- SwiftHum · 5 min read
Why the application node — not the database — is authoritative on balances
An offline-capable P2P payment system can’t trust the database as the single source of truth for a balance. Here’s where authority actually has to live, and why.
Read the write-up → - QuickBite · 5 min read
Catching a silent-loss bug on the Paystack settlement path
The worst payment bugs don’t error — they quietly drop state while everything reports success. How a settlement-path gap on QuickBite could hide, and how to make it loud.
Read the write-up → - Cargoland · 6 min read
Exactly-once push across FCM and APNs with an outbox + dedup key
Push notifications are at-least-once by nature. Delivering an order alert exactly once across two platforms means designing for duplicates instead of wishing them away.
Read the write-up →