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 84 archive entries
Page 2 of 4
Release-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteProtecting the data contract: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteObservability before production: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Security enforcement in Apex
Apex can execute with privileges that require developers to enforce the intended access model deliberately. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily note