About
Where this started
Early in my career I watched capable people spend hours on work that had nothing to do with why they were hired. Not because they were disorganized, but because no one had built the thing to do it automatically. I wrote a script, the problem went away, and my department head put me on a team to find and fix problems like that full-time.
That's been the shape of my work for over twenty years. Find the thing that shouldn't require human attention. Build the thing that removes it.
Where it's going
The same pattern I've seen in enterprise environments exists everywhere. The plumber who's the best in his county but spends Sunday nights chasing invoices. The landscaper whose crews do excellent work but whose scheduling lives in a spreadsheet that breaks. The contractor who closes jobs fast but can't get expense tracking to stop eating her weekends.
These aren't technology problems. They're friction problems. That's the thing BitSalt exists to do — build the software that removes it, and keep it running once it's built.
Where we are now
I spent nearly twenty years building web-based applications—the full stack, from database to UI, across industries that don't have much in common except that they had problems worth solving. Four years ago I moved deliberately into AWS and cloud infrastructure, because that's where the leverage had shifted. I now work across both: application development and the cloud layer underneath it.
That's the work now: building new systems from an idea, and rescuing business-critical applications that have outlived their original platform — often for the same kind of client, sometimes in the same year. The same instinct that made me write a script to remove a manual loop twenty years ago applies to both. Modern development tooling has changed what's economically possible on either side: a rescue that wasn't worth doing by hand is worth doing now, and a custom build that would once have needed a much bigger team is something one shop can deliver — with a measured guarantee behind it either way.
Who should reach out
If your business runs on software that's past its prime — end-of-life platform, original developer gone, a codebase nobody wants to touch — I want to hear about it. And if you've got an idea for something that doesn't exist yet, the same is true: tell me what it is. People deserve software that actually works and keeps working — that's the whole reason any of this exists. Not a sales call. Just a conversation about whether there's a path forward.