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

Connascence of Manual Task

The power of the concept of connascence resides in the fact that it is not just limited to code! Let's see this real life story to understand better the worst type of connascence of all.

I was once in a team that was building a new service for consuming messages from a new queue. The "classic" way they used was to configure a list of messages in the configuration, and for each message, configure a handler. So, for every new message, they had to add not just the handler, but also an entry in the configuration; hence, the two were connascent.

While sometimes this is unavoidable, I always try to minimize connascence, and I tried to remove it. So I decided to make the new service slightly different, smart enough to self-configure at startup and removing the connascent step of the configuration line. The result was great when testing it locally, but when the code was promoted to the integration environment, I discovered that it didn't...