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.
12 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.
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.
Nothing logs a 1:1. No ticket closes when it's over, and its best outcome is a prevented problem, which no system can count. Here's the 30 minutes a week I protect for each person, the short document that runs it, and what protecting it actually costs me.
Tech debt you can see, point at, and put on a ticket. Culture debt gives you none of that...it compounds quietly in the norms and the trust until it shows up in the product. Here's how one small team went into it, why the reward quietly beat the values everyone said they held, and why the trust took over a year to rebuild.