Whether you’re a new developer or you’re fairly experienced as a programmer, you’ll come to realize that the amount of time you’ve worked at a jo...
For further actions, you may consider blocking this person and/or reporting abuse
Actually, Refactoring by Martin is quite fresh (if you're talking about the new one). I've been wanting to grab that book since last summer, but decided to wait for the new one. Have had it for a few weeks now but still reading another book atm.
Edit: I just saw that you linked to the new one 🤦♂️
Haha. All good, man! I love the new book. What's the other book you're reading?
Finished clean code last year and now i’m reading Life 3.0 not really dev related, but interesting look on our future, and the future of AI. Starts of with a a small made up story that makes so much sence its scary. And then it starts looking at whats really going on and the problems we’re facing or going to face in the field of AI
A problem I always find when I try to read books like these is that I don't find them very engaging, I don't know if it is because of a lot of technical language or what. Does this happen to you?
I found most of the books on this list pretty engaging, with the exception of Design Patterns. I realize it's important, but I found it dull to the point of being unreadable, especially if your comfort zone is outside of Java/C#.
Definitely. Some leads swear by it, I think "Head First Design Patterns: A Brain-Friendly Guide" is a way better introduction to design patterns. I probably should have listed that one instead!
Hey Lucas, I'd definitely say that's a common thing. I never really found reading programming books in university to be "fun"; they all just kind of felt like work to me.
I think the moment that reading technical books became interesting to me is the very moment that I started having technical problems that needed to be solved.
For example, I have a codebase on a project that is over 3 years old and 100K lines of code. When output on new features started to slow down, I realized that my software architecture skills weren't quite up to par- so I started reading Clean Architecture, then read Domain-Driven Design. I found that having an actual project or product to apply the things I was learning to actually made it fun. I couldn't wait to figure out how to improve my code... which I was personally invested in!
Thanks for your reply. I can relate to this but I also think books like this should be more engaging, for example The Manga Guide to Databases, which is basically a comic in which you learn relational databases.
That's amazing... I can't believe that exists!
I think we're in a good place now though where we're going to start seeing more content like this. As I mentioned in the article, not a whole lot has changed about software engineering principles over the past 20 years. There's great potential for people to come up with creative ways like this for people to teach it to others. I love that.
Hi Khalil, thanx for your great post,
IMHO these books not are only for juniors Devs
They have a lot knowledge inside that maybe be useful along software development career ;)