I’ve always believed that knowledge travels faster than code. Over the years, these books, newsletters, and podcasts have shaped how I think about building systems, leading teams, and growing as an engineering leader.
This isn’t a complete list, but just the ones that stuck with me. The ones I return to. The ones I push into people’s hands when they ask, “what should I read?”
Start Here
The ones I hand over first.
Read this five years into my career. Changed everything about how I approached readability, testing, and maintenance. Stop writing code for compilers; write it for humans.
The red book. Much nicer and more precise than the blue one, and the one I hand over now. Evans gave us the ideas; Vernon shows you how to actually build with them.
The algorithms book that doesn’t feel like homework. Clear examples, digestible chunks. Perfect refresher before interviews or when you need to remember why hash tables exist.
Your roadmap from tech lead to CTO. Camille Fournier nails every stage. I reread different chapters depending on where I am. Currently dog-earing the VP section.
Will Larson’s guide is the most practical engineering management book I’ve found. Real tactics for hiring, team dynamics, and scaling orgs. The appendix alone is worth the price—a goldmine of paper recommendations.
DevOps wrapped in a novel. Sounds cheesy, but it works. Read this when you’re struggling to explain why “just ship faster” isn’t a strategy.
More Books
Books that changed how I write code, and the ones that helped me not suck at leading people.
The blue book, and still where the ideas come from. It taught me to speak business language in code. Ubiquitous language and bounded contexts aren’t buzzwords—they’re how you survive complex domains without losing your mind.
Martin Fowler’s catalog of “how to improve code without breaking it.” I still reference specific patterns from this book when reviewing PRs.
Uncle Bob’s follow-up to Clean Code. Less about code, more about structure. Helps you avoid the architectural mistakes I made early in my career.
Google’s SRE bible. First half will feel familiar if you’ve done on-call. Remember: what works at Google scale might be overkill for you. But the principles? Solid.
Hit differently when I was navigating the IC vs management fork. Practical roadmap for senior ICs who want impact without the title inflation.
Solid foundation for VP+ roles. Strategic thinking, org design, board dynamics. Wish I’d read this before my first CTO gig.
Newsletters
I’ve tried dozens. These are the ones I actually read every week.
Podcasts
What I listen to while brewing coffee or on long flights.
My podcast. We talk leadership, culture, and the messy reality of building engineering teams. Real stories, no corporate speak.
Fresh perspectives from three women engineers. Shorter episodes, diverse topics. Refreshing take on the industry.
Weekly K8s news and community interviews. Essential if you live in the cloud-native world.
Weekly Go discussions. Whether you’re deep in Go or just curious, solid conversations about the language and ecosystem.