Themes live in the … menu up top. Most of them are albums.
Steady the platform. Then build.
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.
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
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.
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?
I built websites long before Salesforce. Now I’m back at it: design, hosting, and how a site runs.
This is where I’m putting that curiosity to work. I’m building this site and trying out small interactive projects, with room to experiment and share what I learn along the way.
shry.dev ─ □
n8@terra:~hello_~/about ~/n8force ~/n8web
FEATURED / THIS SITE
shry.dev
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.
A digital playground for n8web projects and ideas. Some are useful, some are just fun. I’m sharing them as they take shape.
shry.dev ─ □
n8@terra:~hello_~/about ~/n8force ~/n8web
01 / CURRENT BUILD
shry.dev
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.
The solar-system view is ready to explore: move through time and select a planet to learn more. I’m working on a nav-console view with closer looks at planets and their moons. The illustration here sketches that direction; the link opens the current version.
Follow the relationships.
Salesforce field notes. How the platform behaves, why, and what a change will touch.
The notes are still taking shape. For now, there’s a small interactive sketch below.