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


Connecting Code Smells with Cohesion/Coupling

In the following table, we have grouped code smells in relation to coupling or cohesion excesses. Because cohesion and coupling are more abstract concepts, we can make use of code smells to help us detect imbalances.

For each row in the Degree column and in the Cohesion/Coupling column, highlight the correct concept and then add a reason in the reason column. After the table, we have listed several sample reasons to use. In some cases, both coupling and cohesion apply.

Figure 11.5: Connecting code smells with cohesion/coupling


For answers, see the Appendices section on the page 388.

Some ideas for the Reason column

  • The method is probably doing too much.
  • The class is probably doing too much.
  • A class knows too much about non-immediate neighbors.
  • The class just delegates behavior and has no behavior or state.
  • The class hierarchy is probably wrong.
  • The class misses...