Most of the hats.

I started as an intern, created that organization’s first Salesforce position, and earned my first certification there. Consulting took me across financial services, insurance, and retail. Then I moved in-house. Each role showed me a different side of the platform.

Admin

how people actually use the org

Developer

how the platform works, and the tools and automation people rely on

Consultant

how projects get scoped, sold, and handed off

Engineer

owning the org after launch, and improving it

Architect

what not to build, and the standards that keep an org healthy

6 certifications Administrator · Advanced Administrator · Platform App Builder · Platform Developer I · Sales Cloud Consultant · Service Cloud Consultant

Not afraid of history.

Every org that’s been live a few years has history: layered automation, forgotten workarounds, the big implementation nobody wants to touch. I take the time to understand it. I don’t route around it.

I’ve been the consultant who hands off an org and the engineer who inherits one. Most of my work now happens after go-live. I trace what the org actually does and steady it. I push for good practice and help the team adopt it. I weigh what’s new against what already works. Then I fix forward.

Learn what the work needs.

Tools change. I learn what the work needs, keep what earns its place, and drop the rest. Right now that includes agents.

On Terra, my Linux machine, I run Omarchy, DHH’s agentic OS. A small team of agents works there. They share context, stay within set boundaries, and hand work to one another. The terminal look of this site comes from there.

At work, I run Echoes: a weekly session where I share what I’m learning with colleagues. Every episode is named for a Pink Floyd album.