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

Alternative Definitions of Simple Design

Since the four elements of simple design express high-level goals instead of low-level rules, they allow for a great degree of personalization in how they are expressed. That's because everyone uses their own favorite set of principles and values to express what is key to achieving these goals. Hence, we have found several different versions of the elements, each one different, yet all expressing the same goals. Here are a few of them:

Definition #1

Definition #2

  • Passes all the tests
  • Expresses every idea that we need to express
  • Says everything once and only once
  • Has no superfluous parts

Definition #3

  • Unit tests tell you when you are done
  • Self-documenting code
  • Once and only once, don't repeat yourself, redundancy...