Salesforce daily archive
730 days of practical thinking.
One retrospective note for every day from 2 September 2024 to 1 September 2026.
Archive dates organise the subject history. They do not claim the notes were originally published on those dates.
Showing 365 archive entries
Page 16 of 16
Failure-first thinking: API boundaries
An API should expose a stable business capability rather than mirror a database or a single user interface. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Master data decisions
A connected estate needs a clear answer to which system is authoritative for each important business fact. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Synchronous or asynchronous
Timing is an architectural decision: a process should wait only when the immediate response genuinely changes the next action. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily note