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

The Moral of the Story

The real reason we achieved a considerable goal that time, however, goes beyond the mere technical aspect. The full exploitation of the great potential of the single individuals was possible only because we set up a fully functional team where everyone was trying to meet each other's needs.

We never grew tired of explaining things to one another, trying someone's new ideas that resonated with others, and generally helping each other every time someone needed it. We were a team of servant leaders where trust, support, and empathy felt natural. We never blamed each other, and together we reviewed improvement points several times without anyone ever feeling personally attached to a piece of code. What a childish concept; it wasn't my code or his code – it was ours.

Creating an environment of truly selfless collaboration allowed everyone to freely try out ideas with the consequence of attaining awesome knowledge and technical implementation...