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


Every case of connascence can be measured over three dimensions: degree, locality, and strength.


Degree is the size of the impact as estimated by the number of occurrences and the number of entities it affects. The acceptability of connascence is strongly related to its degree: the higher the degree, the higher the pain when a modification is needed. We should aim to have the minimal possible degree.


Locality is the closeness of the affected entities with respect to each other in terms of abstraction. The closer the better and the more acceptable (leading to cohesion). On the other end, connascence of entities that are very far apart from each other is often an indication of design or architectural pitfalls. We should try to keep the connascent elements as close as possible. If you remember the Law of Demeter, it is meant to limit the distance of method calls, hence acting on the locality.


Strength is the likelihood that connascence...