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 121 archive entries
Page 3 of 6
The decision before the tool: Feature adoption decisions
New platform capability creates value only when it solves a prioritised business need and has an accountable owner. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Release communication
Users need to understand the few changes that affect their work, not receive a copy of the complete release notes. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
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 noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily note