Fourteen years on the platform.
I steady orgs with history, then build. I learn whatever the work needs.
Sites and experiments.
Salesforce field notes.
Themes live in the … menu up top. Most of them are albums.
Fourteen years on Salesforce have put me on both sides of a handoff. I've delivered systems as a consultant and inherited them as an engineer. Being responsible for what happens after launch has shaped how I build.
I start with the organization as it is: the people relying on it, the decisions behind it, and the limits we're working within. I trace how things connect, preserve what works, and fix forward. Each change should make the next one easier to understand and maintain.
That takes shared understanding. I help set standards the team can use, explain the tradeoffs, and share what I'm learning. Steady means we understand what we're building on and can move forward with confidence. I'm still hands-on, still curious, and always learning what the work needs.
Architecture and solution design, hands-on.
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.
6 certifications Administrator · Advanced Administrator · Platform App Builder · Platform Developer I · Sales Cloud Consultant · Service Cloud Consultant
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.
Explore n8force/ ↗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.
Hiring for Salesforce architecture, or want to compare notes?
Find me on LinkedIn ↗I built websites long before Salesforce. Back to HTML, CSS, and JavaScript again. I’m having fun building things I want to use or just play around with.
FEATURED / THIS SITE
This site is my return to building for the web. Plain HTML, CSS, and JavaScript, with a terminal-inspired layout and themes drawn from records I love. I’m refining it as I go.
Back to the front door ↗A digital playground for n8web projects and ideas. Some are useful, some are just fun. I’m sharing them as they take shape.
01 / CURRENT BUILD
This site is my return to building for the web. Plain HTML, CSS, and JavaScript, with a terminal-inspired layout and themes drawn from records I love. I’m refining it as I go.
Back to the front door ↗02 / IN DEVELOPMENT
The solar system from 3000 BC to 3000 AD, built from JPL and NASA data.
Explore Orbit ↗Orbit is now a nav console. One clock runs the map, the target panel and the moons. It adds moons for six worlds, 26,566 named asteroids, inner and outer zoom, and a longer timeline. Every image and number says where it came from.
TBD / MORE TO COME
Salesforce field notes. How the platform behaves, why, and what a change will touch.
Early. The notes aren’t written yet. The sketch below is the idea.
An interactive sketch of objects and agents.
Select an object above. There’s always a log.