I received the call from my sister.
She has called me before on similar occasions.
Sometime early this morning my grandmother passed away.
That is two parents and four grandparents now gone.
I feel untethered.
Designing for Scale: Why I Default to Declarative Before Code
I can write Apex. I often do. But when I design systems, my first question is always: Can this be built declaratively and maintained by a future admin?
Why?
Declarative tools like Flow and Custom Metadata are faster to deploy
They’re easier to maintain, especially in smaller teams
They keep the business logic closer to the surface, not buried in code
Permission Audits Aren’t Just for Security Reviews
Most teams only think about permissions when something breaks or there’s an audit. I treat permission reviews as part of ongoing system hygiene.
Every quarter, I:
Run Permission Set and Profile audits using custom report types
Compare assignments to actual job roles
Remove “temporary” permissions that were never revoked
Optimizing Lightning App Performance Without Sacrificing UX
When Lightning pages get cluttered, user adoption drops—and performance tanks. This year I focused heavily on page performance optimization while keeping layouts intuitive.
What worked:
Replacing overused Related Lists with curated Dynamic Related List – Single components
Hiding low-priority fields and sections behind Dynamic Forms rules
Moving resource-heavy components (like reports or LWCs) to secondary tabs
Cross-Object Formulas That Actually Perform Well
Cross-object formulas can be elegant—or they can become performance bottlenecks. The difference is in how you build them.
I’ve learned to keep them lean:
Limit how many relationships you traverse (e.g. Parent.Parent__r.Contact__r.Email)
Use text outputs instead of nested IF statements when possible
Avoid unnecessary references to formula fields within formula fields
