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 4

Classic TDD III – Transformation Priority Premise

As tests get more specific, code gets more generic.

– Robert C. Martin

When a friend mentioned the Transformation Priority Premise (TPP) in a mob session we were doing in the Arctic region of Finland, I was baffled. I had been practicing Test-Driven Development (TDD) for many years and considered myself an above-average practitioner, yet I had never heard of TPP. As soon as I had a moment with my friend, I grilled him with questions and then spent the night in my cabin learning it.

TPP is quite important in the context of TDD as it defines obvious implementation. Before finding out about TPP, I had been using instinct/intuition, experience, and feedback. TPP brings a bit of process and rationale to evolving code.