How I Think
The thought that keeps showing up in almost everything I build.
“This should be easier.”
That's the thought behind almost every project I've enjoyed building: the internal tool nobody asked for until they saw it, the dashboard that replaced a week of manual reporting, the platform that finally gave a team visibility into work they'd been tracking by hand. It's less a mission statement than a reflex: when something feels harder than it should, I want to go fix it.
Why internal tools
I'm drawn to the software that runs quietly behind the scenes: internal platforms and developer tooling that a team depends on without thinking about it. Workflow Intelligence exists because engineering leadership shouldn't have to manually cross-reference three different tools just to know where things stand. That's the kind of problem I find genuinely satisfying: not glamorous, but real, and immediately felt by the people who use it.
How I get there
My background is in physics before it was in software, and that still shapes how I approach engineering: understand a system before you change it, model it before you build it, and trust data over intuition when the two disagree. Given the choice, I'll ship something boring and reliable over something impressive and fragile.
Where AI fits
AI removes the repetitive parts of my process (boilerplate, scaffolding, first drafts of things I already know how to build) so I can iterate faster on the parts that actually need judgment. It doesn't replace understanding the problem; generating code was never the hard part. I use it to spend more time solving the right problems, not to avoid thinking about them.
What I'm building now
Right now that means Workflow Intelligence at RocketGate: replacing status meetings, spreadsheets, and manual reporting with a single place to understand how engineering work is actually moving. It's the clearest example of how I like to work: find the friction, build the thing that removes it. If you're curious what this looks like in practice, Workflow Intelligence is probably the best place to start.
Outside of software
Outside of engineering, I'm probably out with my dog, working through a mid-90s Japanese project car that has strong opinions about being finished, or enjoying a good craft beer while thinking about none of the above.
Let’s Work Together
Interested in working together or have a question? Reach out and let’s talk!