Book Image

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
Book Image

Agile Technical Practices Distilled

By: Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia

Overview of this book

The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You’ll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You’ll then learn to safely change the design of your code using refactoring. While learning these techniques, you’ll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.
Table of Contents (31 chapters)
Free Chapter
Section 1
Section 2
Section 3
Section 4
Chapter 21
License: CyberDojo

Chapter 7

Design 3 – Code Smells

Design is choosing how you will fail.

– Ron Fein

When I started my career, I spent most of my learning efforts going after specific technologies, trying to understand them in as much depth as I could. As years went by, I started realizing that this was a fruitless path in the long run. Technologies are constantly being hyped and doomed. Part of the game for me used to be guessing what the next thing would be. Sometimes I got it right, sometimes not. Eventually, I stopped chasing specific technologies and started learning more about things that have been relevant and fundamental for many years.

Object-oriented design has not changed much in the past 20 to 30 years – perhaps even longer. What I did not know is there is a price to pay for following this path. Suddenly, I was no longer the one that knew the most about a specific technology on the team. Sometimes, I felt frustrated for not knowing some detail...