That’s the one I’d underline for every junior I’ve mentored. The idempotency example nails it too, same exact payment-retry scenario I’ve debugged, it never shows up in interviews but it’s half of what separates code that survives production from code that doesn’t.