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 5 of 16
Security by design: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: 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 access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: 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 access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: 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 access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: 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 access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Integration observability
A connected process needs end-to-end visibility across platform and team boundaries. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Platform limits as architecture
Governor limits encourage efficient multi-tenant design and must influence architecture from the beginning. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Error recovery
Failure handling is part of the business process, not a technical appendix added after the happy path. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily note