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.
When making something gets cheap but judging it stays expensive, the cost slides downstream...social media did it to your feed, AI code generation does it to your repo. The difference is a bad post washes away by morning, and a bad merge sits there for years.
The risky PR is rarely the big one...it's the one carrying money code, a migration, or a red build, regardless of size. Here's what I look for when one lands, and the product I'm building so senior attention goes where the risk actually is.
Deleting a year-dead feature flag turned a forgotten feature back on and broke production...here's why flag cleanup is a runtime change, not tidying, and how the context you need decays while the flag sits there looking harmless.