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
1
Section 1
7
Section 2
13
Section 3
19
Section 4
25
Chapter 21
28
License: CyberDojo

Highlighted Code Smells

In our experience, we have found that the most dangerous code smells are: Duplication, Primitive Obsession, Feature Envy, and Message Chains. For that reason, we decided to highlight them, especially the last three, as we have already paid enough attention to duplication in previous lessons.

Code Smells Hierarchy

Primitive obsession, feature envy, and message chains lead to many other code smells and should thus be dealt with as soon as possible.

Primitive obsession

  • Duplicated code
  • Shotgun surgery
  • Divergent change
  • Long parameter list

Feature Envy / Inappropriate Intimacy

  • Lazy class
  • Data class
  • Middleman
  • Data clumps
  • Long method
  • Large class
  • Duplicated code
  • Shotgun surgery
  • Divergent change
  • Long parameter list

Message Chains

  • Data clumps
  • Duplicated code

Primitive Obsession

Don't use primitive types as substitutes for classes. If a data type is sufficiently...