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 42 archive entries
Page 1 of 2
A practical architecture review: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Lightning component boundaries
A Lightning Web Component should own a coherent interaction rather than accumulate an entire business process. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteThe decision before the tool: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily note