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 5 of 6
Making team hand-offs work: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Apex service layers
A service layer gives business operations a stable home outside triggers, controllers and transport-specific code. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteGovernance without gridlock: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Security enforcement in Apex
Apex can execute with privileges that require developers to enforce the intended access model deliberately. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Lightning component boundaries
A Lightning Web Component should own a coherent interaction rather than accumulate an entire business process. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Apex service layers
A service layer gives business operations a stable home outside triggers, controllers and transport-specific code. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteFailure-first thinking: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Security enforcement in Apex
Apex can execute with privileges that require developers to enforce the intended access model deliberately. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily note