Blog

Most merge standards are wiki decoration. What makes a team actually follow them isn't the list...it's enforcement, consistency, and the why.

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.

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.

Building software is like traveling between destinations. In our case, it’s traveling from Problem...

Hello, hello! So last week we learned about using your own inbox to capture all your to-dos into a...

"If you can't explain something to a first-year student, then you haven't really understood."...

Ever feel like you're juggling too many tasks, and letting too many things fall through the cracks?...

Let's face it: in software engineering, change is as inevitable as bugs in a first release. Yet, for...

Once again, I'd like to start this week's post off with a question. After last week's post we know...

Continuous learning. Ask any accomplished person in the world today and they'll tell you this is one...

Hello hello 👋 I'd again like to start this week's post off with a question. You have your todo list...

Let's face it: the world of software development is massive, and it's only getting bigger. With new...