Book Image

Agile Technical Practices Distilled

By : Santos, Consolaro, Di Gioia
Book Image

Agile Technical Practices Distilled

By: Santos, Consolaro, 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

Connascence of Timing

Connascence of Timing (CoTm) happens when the success of two or more calls depends on the timing of when they occur. The concept is not very different from CoEO, but here we have an explicit relation with the point in time the call gets executed, not just before or after.

One of the most classic occurrences of CoT is race conditions in multithreading. You'll find another example when you see in the code something like Wait, Sleep, or Timeout followed by an actual arbitrary explicit timespan.

The problem with CoTm is that we usually are not in control of the time, so it obviously has the potential to introduce great flakiness into the system. And intermittent problems are usually the hardest to identify and resolve. That's why we feel that it's always a good idea to try to avoid CoTm like the pox, when possible.

Sometimes, however, we can't really get rid of it. For example, think of some integration tests for a Service Bus. We always...