Curated Content: April 2021

A few pieces of content I thought were worthwhile from the month of April.


There was a bit of a theme this month personally focusing on code reviews, both in my writings, and in my readings. Here are two great articles highlighting the counterpoints to code reviews, what sucks about them, and alternatives. (Spoiler: it's pairing. The alternative is pairing.)

I Probably Hate Your Code Review Process

I Probably Hate Your Code Review Process
One thing that people quickly realize about me is that I hate lots of things. Partly that’s because I tend to be very critical, partly because I am a little too candid for my own good, partly because…

While I'm bullish on code reviews on the whole like the author, there are many things about them that are sub-optimal. Remember that when looking at your process. You may want to reach for pairing more.

Those Pesky Pull Request Reviews

Those pesky pull request reviews
No one wants to review pull requests. This is a sign of a deeper problem than “people aren’t following the process”

Jess (I hope I can call her Jess), always puts out great content, and this is no exception. Highlights the ways that queued/async code reviews are anti-patterns for continuous flow, and how to address that.

TDD: Show Your Work Designs

TDD: Show Your Work Designs
I was reading Brian Marick’s write up of his experience with Hillel Wayne’s budget modeling experiment . Toward the end of the exercise, ...

This post highlights a really interesting technique I've used previously for debugging and adding tests to a previously difficult piece of code, by breaking it down and "showing my work" along the way.

Trapped in the Technologist Factory

trapped in the technologist factory

I disagree with the author of the above that technology isn't improving. I think some things are clear improvements over the status quo. TypeScript over JavaScript. Elixir over Ruby. Rust over C. But on the whole I think they make a lot of really interesting points about the system the industry is designed to build versus the value it purports to or ought to be building.

Write a Good Dockerfile in 19 Easy Steps

codefinger - blog
Deploying with JRuby, Healthy Programmer, Remote Pairing, Heroku

A great checklist for working with Dockerfiles. If you work with them, start here.


The Power of Moments - by Chip and Dan Heath

A great read on what makes moments impactful, in life, career, and leadership. More than just an inspirational read, it includes guides to how you can craft more meaningful moments for yourself, your customers, your family, or anyone else you'd care to craft a moment for.


Me to myself regularly, and also accidentally to my team when trying to support them.
A great thread highlighting how failures look like they occur at a single point in time, but usually mean several things had to go wrong in order for the bad outcome to occur, and the incentives that result in this.
An old tweet, but one I need to mount on the wall of my home office.