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.
A consistent coding framework is what makes 100 developers behave like one team
A framework is a core set of classes, the conventions around them, and someone enforcing both. Its product is that every team's code has the same shape, so anyone can review anyone's work and the next platform change is three edits, not every class. That only holds if someone owns it.
Partner-first delivery is a trade, and most orgs only read one side of the contract
A delivery partner sells speed, capacity and accountability, and those are real. You pay with knowledge, design authority and the ability to judge the work, none of which appears on the invoice, and whether that trade suits you is knowable up front.
3,000 mThe architecture
For architects and anyone who draws boxes for a living, Salesforce or otherwise.
Everything at 3,000 mYour AI code reviewer still needs a linter
A linter is a smoke alarm and an LLM is a building inspector. Keep linting as the deterministic gate (security rules on every touched file, everything else on changed lines) and let the model review intent and suggest repairs that go back through the same gate.
300 mThe delivery team
For tech leads, admins, developers and whoever carries the pager.
Everything at 300 mNothing filed at this altitude yet.
Nothing filed at this altitude yet.