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

What is Pair Programming?

Pair programming is a disciplined approach to writing software. It assigns specific roles and responsibilities to each pair member, defines strategies to switch positions, and promotes breaks to avoid pairs exhausting themselves.

Pair programming is about shortening the feedback loop when writing code. It is easier to change software as we write it. To validate our ideas, we can discuss design choices in real time with an unbiased peer. If we have an extra person reviewing while we write code, we reduce the feedback loop to a few seconds. And the faster the feedback, the faster we converge on a quality-rich solution. Lean thinking applied!


Pair programming requires a high level of maturity from peers.


Pair programming should be a choice, not an enforced practice.