About

Background

I came to Salesforce architecture with a background in IT, security and platform development. I’ve worked across everything from Splunk and Citrix to Apex and Flow, and I’m always looking for ways to build smarter, cleaner systems that actually make people’s lives easier.

These days that mostly means Salesforce: architecture and Apex, integrations, Flow and Agentforce, and Marketing Cloud alongside the core clouds. The work page goes into each of them.

How I work

• Bulk-safe by default. Triggers and automation written for a thousand records, not one, with logic layered into handler classes.
• Tests that behave like production. Realistic test data and mocked callouts from the start: the fastest way to debug is a test that already reproduces the problem.
• Secrets stay out of code. Named Credentials for every integration, never hard-coded endpoints or keys.
• Loosely coupled. Platform Events and asynchronous Apex wherever a process doesn’t need to wait.
• Agents with clear jobs. Agentforce agents with precise instructions, the permissions they need from day one, and a record of every session.
• Automate the busywork. Publishing, building and deploying belong in a pipeline.

Learning in public

I learn best by doing, then writing it up. In 2025 that meant a weekend cert sprint, with the Agentforce Specialist and Marketing Cloud Engagement Administrator certifications and the Apex Specialist superbadge, followed by five days of advanced superbadges on the way to Platform Developer II.

The blog collects those write-ups, along with walkthroughs like using Agentforce with Flows.

The homelab

At home I run a small lab on TrueNAS, with Dockge for containers and Nginx Proxy Manager in front, plus a Splunk server on a free developer license. The Splunk homelab series starts with building that server from scratch.

Get in touch

Always up for a good Salesforce puzzle. The contact page has email and everywhere else I am.