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 365 archive entries
Page 6 of 16
Security by design: API boundaries
An API should expose a stable business capability rather than mirror a database or a single user interface. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Master data decisions
A connected estate needs a clear answer to which system is authoritative for each important business fact. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: 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 how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteContaining technical debt: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily note