Merge Standards That Actually Get Followed
Most merge standards are wiki decoration. What makes a team actually follow them isn't the list...it's enforcement, consistency, and the why.
Hey, I'm Jake.
I build fast, solve problems, and lead engineers.
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.
Currently Reading
Latest Blog Posts
Three Targets I Set for My Engineering Team
The three targets I set for my engineering team — PR size, open-to-merge time, and change failure rate — and why these are the three that matter.
The Code Review Checklist I Actually Use
Most code-review checklists ask "does this work?" The harder question is "what happens when it doesn't?" Five things I check on every PR that the standard checklists miss... plus the comment grammar that makes reviews actually move.