I build fast, solve problems, and lead engineers.
Right now I'm building Merge Lantern, risk intelligence that tells small teams which pull requests need senior eyes before they merge.
I'm an Engineering Manager and Technical Architect. I turn ambitious roadmaps into shipped reality, broken and bloated systems into modern marvels, and chaotic sprints into calm, dependable releases — all without losing the human part along the way.
13 years in and I still love this stuff...the hard problems, the good teams, the moment it all clicks. Poke around; the rest of the site fills in the details.
My team reviews code faster than it did before coding agents showed up, and I'm still finding real problems in code that already shipped. Turns out those two things can both be true at once...there's a study that explains how. Here's what actually broke (it wasn't my team), and what I'm doing about it.
On a lot of teams, code that a pair of devs wrote usually gets a lighter code review. Nobody wrote that rule down and nobody voted on it, but pairing earned it. Here's what the research actually says about that discount, why it's never one flat size, and what happens when dev + agent starts getting filed under the same category.
A one-line warning in my deploy log took my site down for thirty minutes. It didn't stop anything, the command exited zero, and it looked like every other line scrolling past. Software risk stays invisible until traffic hits it, and that invisibility is why the work that prevents incidents is the first thing a deadline cuts.