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

Chapter 19

Story of Team C

You have your way. I have my way. As for the right way, the correct way, and the only way, it does not exist.

– Friedrich Nietzsche

Imagine you are in a big team, without a strong leadership everyone is going in a different direction. Just a few seem able to reach agreements, owning and sharing principles, and discussing how to apply them best for the collective benefit. They spend hours helping each other, often pairing together over the same code. But they are the minority and are largely outnumbered by egos and wannabe heroes.

Nevertheless, facts are with the few, which slowly over time conquer respect. But far from making the impact they want, the team as a whole is still delivering neither quality nor quantity, strangled by an unreachable consensus and inevitable, growing technical debt.

Then, imagine one day they told you, "If we don't deliver something significant in four months, our project will be dumped...