This question pops up on every form of media out there. "What books should I read to be a better developer?". I've answered this a ton of times. On Twitter, on Dev.To, Reddit, and everywhere else.
I figured it might be a good idea to put the list in a single post I can always link to.
Note: I am using Amazon affiliate links where I link to the books.
Clean Code: A Handbook of Agile Software Craftsmanship
I NO LONGER RECOMMEND THIS BOOK
The author has a lot of problematic views about race, women, etc. Please do not buy this book or contribute to the author.
The Pragmatic Programmer: From Journeman To Master
I'm still about halfway through this book. This book is amazing for anyone starting out a career in development -- and anyone well into it. I found it shows and explains various scenarios you'd find in the real world and then it discusses strategies to tackle them. It features tons of ideas about how to keep your code clearly separated, how to think about concurrency, how to address code that needs to clean itself up, and so on.
Probably my favorite part of the book is the discussion around what "prototypes" are for, how to use them, and so on. And then it discusses the idea of a "tracer bullet" (which I've discussed in my post My Experience Running Development At A Startup) and totally won me over and changed how I do development.
Game Programming Patterns - GMP free to read on the web
Before I get into it, you might be thinking, but why game programming? I'm a web developer and this book is just as relevant to web devs as it is for game devs. This book is by far the best resource I've found that discusses common (and well-known) programming patterns -- from their advantages, to their drawbacks, trade-offs, and their details. All neatly written to be easy to understand.
There are quite a few that I absolutely recommend reading about:
- Object pool
- Dirty Flag
- Singleton -- because that's how your node imports work!
- Observer
I also suggest reading the game loop and update method patterns if you're into gaming.
Non-Violent Communication
This might seem off-beat but despite being a non-programming book, I found it extremely useful in terms of communication and applying empathy to my work. Not only that, but I found it useful in my interactions with my teammates and my other co-workers. It covers a few key concepts:
- how to ensure both parties are in full understanding of a concept
- applying empathy in stressful situations
- value of honesty
- value of expressing your own needs
All of those have been key in my career in one way or another. Here's a dirty secret: my own team focused on communication with each other and with our manager heavily. Improved communication lead to greater job satisfaction (personally) but it also lead to better code, feature releases, better conversations around development roadmaps, and so much more. We didn't use NVC but we did make big changes into how we're organized
Books I haven't Read (Yet)
I have a stack of books in my GoodReads that I want to read, and even a longer stack of books I keep in my head. I can't personally vouch for these but I do see these come up over and over again on Twitter, here, and elsewhere:
CSS Secrets
A book that made waves when it dropped, CSS Secrets by Lea Verou is a book focusing on techniques and tips and programmatic solutions to your CSS problems and how to practically write CSS. If you're not sure this is for you, check out one of her many talks.
Refactoring UI
Refactoring UI by Adam Wathan and Steve Shoger has been making rounds on my radar and I think it's a worthwhile book to look into. I haven't personally had time to check it out but I've heard of Adam's courses that people love and I have closely followed the development of Tailwind CSS which is his CSS framework.
Top comments (28)
Clean Code
I am currently reading this book. Only 50% done. But many things have stayed with me:
So I'm not as concerned about 100% coverage and I'm not a big fan of TDD. I think those two principles I'm moving away from over the years.
Health is huge though. Good sleep, good diet, and a good keyboard go really far.
I did not meant to point 100% coverage or TDD. We can debate later on.
But code needs to be tested for sure. Manually or automated for sure. - That was my point.
These are the books that made a difference in my career, although some are getting dated:
Clean Code
Code Complete
Peopleware - about people more than code, dated I think.
Joel on Software - a compendium of the best posts from Joel's blog. Kind of dated now.
Very pleasantly surprised to see Rosenberg's NVC book here. It is indeed helpful as a programmer, I've found as well. Also recommend books on Servant Leadership, though I can't recall off the top of my head right now which one of those I read.
Another recommendation: Pragmatic Thinking & Learning (also by the Pragmatic Programmer folks). pragprog.com/book/ahptl/pragmatic-...
Also, because the industry is for some reason obsessed with pulling all-nighters and producing burnouts: Why We Sleep is a great book that will make anyone have second thoughts about ever pulling an all-nighter ever again: goodreads.com/book/show/34466963-w...
Working Effectively with Legacy Code by Michael Feathers is a gem. Given you'll mostly work with legacy code, which includes stuff you wrote 6+ months ago, this book gives really useful practical advice on getting existing code under test.
I've given away too many copies of this book to colleagues. It's invaluable.
Thank you for recommending this here. I would go as far as call it the most valuable I've read the last 4 years. I read clean code, clean coder, pragmatic programmer, mythical man month, the goal, the Phoenix project (really good), and some more that I can't recommend.
I have read Clean Code before and after coming off a year of leave I am looking forward to re-reading it! The other book I have just started is The Phoenix Project, which is a tale of DevOps/IT success in the form of a novel.
I haven't read Clean Code in years, but I'm wondering if you can recall the parts that you mentioned you no longer agree with. I'm curious about what ideas the industry has moved beyond since that book one came out.
Adding some more reading stuff:
amazon.de/Release-Production-Ready...
amazon.de/DevOPS-Handbook-World-Cl...
amazon.com/Practice-System-Network...
amazon.com/Practice-Cloud-System-A...
You have the classic coder books, so I will add these
Radical candor - people management
Never split the difference - empathy, dealing with people
Scrum Mastery: From Good To Great Servant-Leadership
The "Game Programming Patterns" sounds interesting, but for the short review you mention (and the objective you want to fulfill with this book) I'd suggest rather "Design Patterns: Elements of Reusable Object-Oriented Software", which might be a bit less application specific
GMP is by far the easiest resource to read on design patterns that I've read. I'm sure there are plenty of others but the language and examples in the book are fantastic. I've been recommending it for years.
Eloquent Javascript is a fantastic resource for getting up to speed with js in general, and a really good starting point for beginners looking to get into js frameworks.
Having an understanding of vanilla js is so important to take advantage of all the different frameworks out there.
I'm a huge fan of it as well but idk how up-to-date the book is with today's JS (ES2015+).