Great systems enforce standards without punishing innovation. I use Custom Metadata to define and enforce those standards across the org.
Examples from real projects:
Controlling which Record Types can trigger which Flows
Defining available options for dynamic automation menus
Centralizing logic that multiple Apex classes reference
Salesforce gives you a lot of ways to integrate—REST API, Apex callouts, Named Credentials, External Services, and more. The trick isn’t knowing what’s possible. It’s knowing what’s appropriate.
My go-to rules:
For real-time sync, I use REST callouts with Named Credentials
For asynchronous or high-volume data, I lean on Platform Events or Change Data Capture
For user-initiated actions, I’ll consider Screen Flows or LWC buttons with Apex
When systems need to talk to each other asynchronously, I reach for Platform Events. They’ve become a core part of how I design integrations and decoupled automation.
Why they matter:
They allow publish/subscribe communication between systems
They’re built for scale and resilience, not just speed
You can trigger flows or Apex in response to events—with zero user action
Most admins react to requests. I prefer to design systems with a long-term metadata strategy in mind.
That means:
Naming conventions for all fields, flows, and objects (FieldPurpose__c, not Custom1__c)
Avoiding unnecessary custom objects when record types or junction objects will do
Grouping flows by lifecycle (create/update, scheduled, utility) and using consistent labels
Component visibility in Lightning pages isn't just about page layout—it’s about security and context-aware experiences.
This year I’ve been refining:
Field-Level Security enforcement in custom LWCs
Record Type and Profile-based visibility on Lightning pages
Using custom permissions to show/hide entire page components
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.
