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 252 archive entries
Page 1 of 11
Testing the business outcome: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteRelease-ready engineering: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily note