Here's a doc I like to use to structure the pre-work design chat that makes later code review a breeze.

Why do some projects ship and others seem to drag on forever? You need 3 people to get this right.

You can't prevent bugs. You'll burn out. Instead focus on making them quick to fix.

A long design phase without shipping kills many software projects. Here's a story from production I haven't shared before.

Been thinking about what needs to be in place for engineers to ship with confidence

effective engineering teams should work *with* their product owner/manager, not *for* them

When working: sync first *then* async

A shift in your code review process can boost your team's productivity. Empower authors to make the call.

Don't get stuck being a critical member of the team.

Team dysfunction where everyone's a soloist? Try this fix: Force the team to work on ONE story at a time.

Ever felt like your software team is just soloists in a trench coat? You may be right!

The secret to effective standups that don't suck