What Book Should I Read to Become a Software Engineer?
I will probably never forget my first day as a software engineer.
Back in the 25's I was hired as a software engineer for a consulting agency in Luxembourg.
I didn't have much experience but I was ready to tackle the single project I was in charge of.
However, on my first day, I was not given a project, I was given a book.
My technical consultant returned (if you're reading this, who I salute!) Probably knew how important it was to set the right foundation as a software engineer.
To this day, I still apply most of the them I read in this book on a daily basis, and I firmly believe that it has a great positive impact on my work.
So today, I want to give back.
For young engineers or more experienced people who want to test their knowledge, here is my top 10 list of the best software engineering books.
1. Clean Code by Robert Martins
2. Design Patterns: Elements of Reusable Object-Oriented Software by Eric Gamma
3. Patterns of Enterprise Application Architecture by Martin Fowler
4. Enterprise Integration Patterns by Gregor Hohpe
5. The Mythical Man-Month by Frederick Brooks
6. Code Complete by Steve McConnell
7. Git for Teams by Emma Hogbin Westby
8. Refactoring: Improving the Design of Existing Code by Martin Fowler
9. The Art of Unit Testing by Roy Osherove
10. Cracking the Coding Interview: 189 Programming Questions and Solutions by Gayle Laakmann McDowell.
Clean Code: A Handbook of Agile Software Craftsmanship by
Probably a great book about software engineering and programming. Every engineer, developer or programmer should have read this book at least once.
In this book, Robert Martin provides a clear and concise chapter about
1. How to write high-quality and expressive code;
2. How your objectives in your coding style are to name your activities, your variables;
3. How to properly test a unit, why it matters, and how to do it correctly;
4. How to choose relevant data structures and why they can make or break a piece of code;
5. How to write a comment But most importantly how not to write a comment;
6. How error handling works and how to properly engineer an exception handling workflow through your application or program.

Comments
Post a Comment