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 252 archive entries
Page 11 of 11
Designing for scale: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Trigger discipline
Triggers should coordinate record-change behaviour without becoming a hidden application framework. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 the decision behaves when volume, users and connected systems grow.
Read daily note