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 126 archive entries
Page 6 of 6
Failure-first thinking: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Lightning component boundaries
A Lightning Web Component should own a coherent interaction rather than accumulate an entire business process. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Apex service layers
A service layer gives business operations a stable home outside triggers, controllers and transport-specific code. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily note