Photo by Matt Howard on Unsplash
When I first started blogging about my salesforce journey, I was learning how to create custom fields and figuring out what profiles and roles even did. Today, I’m writing Apex, designing flows with intent, and building automation that supports real teams and real business goals.
Here’s what I’ve learned along the way:
Listen before building—users describe symptoms, not systems
Design for change—nothing you build stays frozen
Keep it human—good tools should disappear into the workflow
Salesforce isn’t just a CRM—it’s a full platform for automation, integration, and user experience. And becoming a developer in this ecosystem means learning how to think in terms of systems, code, and business process—all at once.
I’m not an architect yet. But I’ve learned to build with clarity, with scale in mind, and with people at the center. That’s the mindset I’m bringing into Year 6 and beyond.
