Papers & Books

Blogs and hot takes are fun but the good stuff hides in primary sources. I like to read computer science papers and books cover to cover and write about what holds up in production and what doesn't.

You get the insights without wading through 40 pages of LaTeX. And when a famous book doesn't survive contact with real code, I'll tell you that too.

Papers and books

4 articles from 2025 show all

June 2025

3 sticky insights from 3 eng management books

Ever feel like your brain is blended and you can't even keep up with the things you're learning? Me too. But the good shit stays.

February 2025

What I learned from Inspired

Products not projects. Outcomes not features. Iterate.

January 2025

What I learned from Accelerate

Accelerate is the empirical research behind books such as The Phoenix/Unicorn Project and (parts of) Software Engineering at Google. I loved it.

The score takes care of itself

Less talking more doing