At Serverless we're constantly educating ourselves to incorporate the latest best practices into our engineering processes so we can deliver the best Serverless toolings out there.
This blog post lists useful software engineering books we've read and highly recommend.
Note: This list is a living document. We'll update it periodically to reflect our recent learnings/recommendations.
We are not associated with any authors or platforms we list here
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code by Robert C. Martin (aka Uncle Bob) is a classic book every software engineer and programmer should read. It teaches you how to write code in a way that's easy to read and understand.
You don't have to follow every single technique, but even adopting some of them will ensure that your code "reads like prose".
Remember that a majority of our time as developes is spent reading code rather than writing it.
And to be honest:
if (isTester && hasBetaAccess) {
return betaTest();
}
return standardTest();is way easier to read than:
return tester && beta ? beta() : default();The Clean Coder: A Code of Conduct for Professional Programmers
This is another great book from Robert C. Martin, the author of "Clean Code".
The main topic of this book is how professional software developers should behave, incluing how they should communicate and work on projects or solve problems.
Have you ever felt empowered and overjoyed after hitting a super tight deadline inspite of being overloaded with tasks in the current sprint? You and your manager should be proud, right?
Read this book and think again...
The Phoenix Project: A Novel about IT, DevOps, and Helping your Business Win
Authored by Gene Kim, Kevin Behr, and George Spafford, this novel about IT operations is not the usual tech book. It's really something you can read before going to sleep without your head spinning with all the complex tech problems you've just read about.
The Phoenix Project is a good read if you want to see how the "wrong work" will negatively impact the performance of your company. You'll learn the different types of work and see how a (fictional) doomed corporation transitioned from being a "poor dog" to a "star".
The Pragmatic Programmer: From Journeyman to Master
The Pragmatic Programmer by Andrew Hunt and David Thomas is another classic every software engineer should read. A true "oldie but goldie".
You'll learn how to approach tackling different problems you might face during your professional career. This book is a little bit dated, but was revolutionary when it was publised in the 90s.
Design Patterns: Elements of Reusable Object-Oriented Software
Even with the rise of new programming paradigms (like Functional Programming), Object-Oriented thinking and designed software is definitely still around.
Design Patterns by the infamous "Gang of Four (GoF)" - Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides - with foreword by Grady Booch, is a great compilation of all relevant architectural patterns you can utilize to make your Object-Oriented software easier to maintain.
The Imposter's Handbook: A Primer for Self-Taught Programmers
Can you relate to the feeling that you just don't know enough? Perhaps someday you might be exposed as a "fraud" because you do your job, but compared to others you're still lacking some knowledge?
This is called "Impostor Syndrome" and quite a common feeling in the tech industry where experienced coders are hired even if they don't have an academic degree.
Some people even find themselves sitting next to a 16 years old who was hired from college because of his coding experience.
But The Imposter's Handbook by Rob Conery has got you covered. It fills your knowledge gaps and walks you through all the topics you'll also learn in a CS degree program.
This will enhance your career, solidify your self-esteem and you can finally chit chat with the Ph.D. who's working in the Machine Learning division.
Refactoring: Improving the Design of Existing Code
Code gets messy over time. That's just a circumstance we cannot change. But what we can change is the complexity of our codebase through refactoring.
The classic Refactoring by Martin Fowler and Kent Beck will show you how you can identify bloated code, and how you can work your way through the old, entangled codebase to a new shiny, refactored one.
The books is old, but still a classic. The examples are Java heavy but can be applied to other codebases, as well.
Is something missing?
Know of a great book that's missing from this list? Great! Just open up a PR by clicking on the "edit" button above or add your favorite book in the comments below!
