If you really want to get better at programming, you
must read these books.
Whether
his career as a programmer lasted a month or ten years, he must have already
realized that programming is complex. He has a lot of languages, design
patterns, frameworks, and he needs to use all of these to meet some business
requirements to create a product.
You are faced with a problem that you have never seen
before. After thinking about it and trying it several times, you decide to
google it and find the topic of stack overflow. The thread has 20 answers to
your problem. Pick one, give it a try, see if it works, and move on to the next
task.
Today, there are many free resources on the Internet. Each
problem has 10,000 different solutions. The tutorials provide an opportunity
for everyone to learn to write code. This is good because it helps develop the community of programmers and software in general. Still, the truth is that the market is flooded with more and more young people who ignore the quality of the code and the fundamental skills of software
development...
Here's a list of books that I think every software engineer
(or anyone who just wants to get better at programming) should read. Some books
provide examples in Java or C, but these concepts apply to any programming
language and will help you become a better developer.
1. Clean Code: A Guide to Building Flexible Software
If you had a book to
read, this is the one. It begins by explaining why clean code is necessary and how it can
and will affect your business. Without a doubt, this is something essential for every developer.
It then provides guidelines for simple things like commenting, naming variables, designing your code architecture, adding or
refactoring that is hard to understand. It's pretty easy to read and will open
up new perspectives if you've never heard of clean code. His team and his
colleagues will appreciate your making sure to apply part of this book.
2. Clean Architecture: A Guide to Software Design and
Structure.
The second book in
the "Purity" series. Today's applications are very complex and often
have multiple components. This book provides advice on SOLID principles and how
to apply them. It also talks about functional and object-oriented programming. I liked this book because it had real-world use cases with lots of
diagrams to aid understanding. It does not hurt to read this book, but it is more for experienced and high-level developers, as it is very
architecture-oriented. However, it will come in handy for anyone serious
about their careers.
3. Clean Coder: a code of conduct for professional
programmers.
The last book in the
"Purity" series. This book is more about soft skills that every
developer should know. It provides lots of tips and strategies for testing, working in a team, timing (which becomes a fundamental topic when you start a business
/ for clients), dealing with pressure, and more. All this can be read in
6-8 hours as a series of little anecdotes.
4. Design patterns: reusable object-oriented software
elements.
This book was written
by the Gangs of Four (Gamma, Helm, Johnson, and Vlissides), a gold
mine. It catalogs 23 design patterns, divided into three groups
(creative, structural, and behavioral). There is intent,
some use cases, pros and cons, and some implementation details for each way. This is a great book to
reference daily as you work on projects and discover some patterns that you
might apply to your business cases. It also provides related templates that you can use instead.
5. Domain-based design: overcoming complexity at the
heart of the software
For some, DDD is the pinnacle of building maintainable and
scalable software. To summarize, DDD argues that business rules must be at the center of its design when developing software. The entire company
must discuss the requirements in the same language (generic language).
DDD is difficult. This requires a lot of technicals
knowledge and actually uses some.
.jpg)
