Every problem looks different depending on how high you stand.
Essays from a Salesforce architect on architecture, AI and design for large organisations, filed by who should read them. Start at your altitude, or scroll all the way down to land.
-
New agent frameworks, weekly
Visibility moderate. Pick the one you can govern, not the loudest one.
-
Platform release notes landed
Scattered breaking changes in security defaults. Pack a test suite.
-
Restructure season
Strong winds through the org chart. Check your sharing model.
Config versus code is a governance decision
Decided in the boardroom, felt in every line of code. Pick one on purpose, write the rule down, then make it boring.
Your org chart is now a security boundary
Why every restructure quietly becomes an access review.
3,000 mThe architecture
For architects and anyone who draws boxes for a living, Salesforce or otherwise.
Everything at 3,000 mThe integration catalogue nobody reads
Patterns only help if people find them before inventing a new one.
Event-driven or request-reply, chosen on purpose
A short decision guide for people tired of the debate.
300 mThe delivery team
For tech leads, admins, developers and whoever carries the pager.
Everything at 300 mAgents need guardrails before they need prompts
What changes when a large team lets AI write production code.
Spec-driven delivery for every feature
Small features are where undocumented decisions breed.
Code review when half the code is machine-written
Deterministic checks for the boring parts, people for judgement.
Naming conventions are an architecture decision
The cheapest standard you will ever enforce.