5 Programming Books you Need to Read

1) Clean code from Uncle Bob

This book was one of the best books I read in my entire professional life. After you read this book you will be more conscious about the need of writing clean code and I bet you will not look back.

From naming variables to code testing, this book covers all the topics you need to improve your code dramatically.

Clean Code: A Handbook of Agile Software Craftsmanship
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year…amzn.to

2) Clean architecture from Uncle Bob

This book like the previous one, is a must to read to every programmer. It will improve dramatically the way you structure and design your software, to achieve high levels of maintainability and correctness in your product.

Clean Architecture: A Craftsman’s Guide to Software Structure and Design (Robert C. Martin Series)
Clean Architecture: A Craftsman’s Guide to Software Structure and Design (Robert C. Martin Series) [Robert C. Martin]…www.amazon.com

3) Grokking Algorithms

This book is an extraordinary and easy to digest guide to the most used algorithms in computer science. Is so easy to read that even non programmers can understand how this algorithms work.

Grokking Algorithms: An illustrated guide for programmers and other curious people
Summary Grokking Algorithms is a fully illustrated, friendly guide that teaches you how to apply common algorithms to…amzn.to

4) Head First Design Patterns: A Brain-Friendly Guide

Software design patterns are a handy tool to have in your box. These are software design patterns that are in compliance with the SOLID object oriented principles:

• Single Responsibility Principle. A class should only have one reason to change.
• Open/Closed Principle. Software entities should be open for extension, but close for modification.
• Liskov Substitution Principle. subtypes must be substitutable for their base types.
• Interface Segregation Principle. Clients should not depend on methods they don’t use (keep it short and simple).
• Dependency Inversion Principle. High level modules should not depend on low level models

Head First Design Patterns: A Brain-Friendly Guide
What’s so special about design patterns?At any given moment, someone struggles with the same software design problems…www.amazon.com

5) Test Driven Development: By Example

Test driven development allows you to program your software in incremental steps, defining first the business logic rules trough tests, see them fail and produce the minimal amount of code to see them pass. At a first sight it seems that you are doing more work than you should, but once you adopt it you will see that you do less code, with more quality and you will have confidence to change your code without worrying that everything will fall apart.