Leaky Abstraction Cost
What a consumer pays when a platform abstraction hides a mechanism they must nonetheless understand to diagnose or tune it.
Every platform abstraction is a bet that consumers will not need what it hides. When the bet holds, the abstraction is pure gain. When it fails, the consumer now has to understand both the underlying mechanism and the abstraction's mapping onto it, which is strictly more work than having been given the mechanism directly.
The failure is most visible during incidents. An engineer whose deployment is failing must debug through a layer that renamed everything and hid the events. It is also visible in performance work: a platform that abstracts away resource requests makes it impossible to tune the thing that is throttling.
The design response is not to abstract less but to make the abstraction transparent — provide an escape hatch, surface the underlying object's identity so it can be inspected, and propagate errors from below with their original detail rather than replacing them with a generic message. An abstraction with a visible floor is cheap to leave; one without a floor traps its users at exactly the moment they most need to get out.