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 244 archive entries
Page 8 of 11
Observability before production: Synchronous or asynchronous
Timing is an architectural decision: a process should wait only when the immediate response genuinely changes the next action. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily notePlanning the migration: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Data-quality ownership
Data quality is an operating responsibility supported by technology, not a cleanup project owned only by administrators. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily note