What does good idempotency code look like?
When does idempotency need a refactor?
What rule of thumb should you remember for idempotency?
When should you avoid a fancy use of idempotency?
How does idempotency affect maintainability?
What state reasoning matters with idempotency?
What naming guidance fits idempotency?
What boundary guidance fits idempotency?
What data-shape guidance fits idempotency?
What failure handling lens fits idempotency?