The more complex your Salesforce Org becomes, the more sophisticated your code/flows... should be.
Sounds obvious, doesn't it?
I think that's one of the biggest misconceptions in Salesforce.
For 95–98% of orgs, simplicity beats sophistication.
Yes, I understand dependency injection, layered architectures, and enterprise frameworks. They solve real problems when you have a team that understands, maintains, and evolves them.
If you have that team, you're in a great position. Enjoy it.
But most Salesforce orgs are maintained by small teams of ever changing Admins, Consultants, or Developers inheriting years of customizations not by the sophisticated tech lead who implemented the fancy framework.
That's why I follow one simple rule:
Every Flow, Apex class, Validation Rule, or other automation should read like a recipe.
Much of the logic I write today still follows the same structure as the first BASIC programs I wrote over 30 years ago:
When this happens → check this → do that → finish.
The language changed. The principle didn't.
That's also the philosophy behind CleanForce. Remove accidental complexity. Refactor relentlessly. Leave behind an Org that people can confidently understand and change.
Because for most Salesforce orgs, simplicity isn't a compromise. It's the better engineering decision.
PS: I'm guilty of breaking that rule myself, still feel bad about it
Book a free 60-minute Salesforce Technical Debt Audit: a score for Usability and Build Quality, and your top cleanup priorities.