Ryan Peterman's Blog

5 Books Every Software Engineer Should Read

Ryan Peterman's photo
Ryan Peterman
·

4 min read

👋 Hi, this is Ryan with this week’s newsletter. I write about software engineering, big tech/startups and career growth. Thank you for your continued readership, we welcomed almost 2000 new subs last week 🙏🤯

Note: There are no affiliate links in my book list. Enjoy!

The goal for my book list is simple. I wanted it to cover the 20% of reading that you need to do to get 80% of the skills you need on the job.

To make sure this list is high quality, I cross-referenced my recommendations against three sources: Hacker News mentions, Reddit mentions, and Amazon reviews. From my research and experience, here are the top five books every software engineer should read.

Introduction to Algorithms — “CLRS” (link)

This book is the most famous algorithms & data structures textbook in the world for good reason. It covers everything you need to know on these topics.

When I read it in college for my algorithms class, I was impressed with how applicable it was for interview prep. All Leetcode questions are applications of the knowledge in this book.

It goes further than just Leetcode though. A basic understanding of common data structures is important on the job. Besides, its popularity and ratings speak for themselves:

Clean Code (link)

Engineers must maintain and modify software to handle business needs. This is much easier to do when code is well organized. This book covers how to write maintainable code.

The knowledge in this book is what helps me write high-quality code and provide useful feedback on code reviews. Given how valuable this book is, it makes sense why it’s so popular and highly rated:

Designing Data-Intensive Applications (link)

System design is a critical skill for experienced developers. This is because senior developers are responsible for their team’s end-to-end systems. Reading this book will help you build modern, scalable systems. I highly recommend this book if you’re looking to expand your system design understanding.

On Writing Well (link)

Writing well is valuable for software engineers. Top Hacker News posts (ex1, ex2) and figures like Paul Graham agree. Yet, engineers don’t get any training on how to write and have to figure it out on the job.

On Writing Well should help; It’s a famous book focused on how to write nonfiction better. I recommend this book over The Elements of Style (the other famous book on writing) because this one gives you general guidelines rather than specific rules to memorize. It’s helped make my writing clearer. Not to mention that it has great ratings and is often mentioned on Hacker News:

How to Win Friends and Influence People (link)

Last but not least, if you only have time to read one book, it should probably be this one. The title is a little strange but hear me out.

Just about everything at your job involves other people. You won’t go far if you’re difficult to work with even if you’re talented. The better you are at working with others, the easier it is to get things done. This book is a great guide for soft skills. The popularity of this book matches my recommendation:

To show you that this recommendation comes from personal experience, here’s my copy of the book. It was a gift from my Dad and is older than I am. It’s also a bit worn since I’ve read it a few times:

Join 6500+ software engineers from companies like Google, Meta, and Amazon who receive new posts and support my work on Substack.

Thanks for reading,
Ryan Peterman

CareerbooksBeginner Developerssoftware development