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
1
Section 1
7
Section 2
13
Section 3
19
Section 4
25
Chapter 21
28
License: CyberDojo

Balanced Abstraction Principle

Sandro Mancuso, in his blog, defines the Balanced Abstraction Principle as follows:

The Balanced Abstraction Principle defines that all code constructs grouped by a higher-level construct should be at the same level of abstraction. That means:

  • All instructions inside a method should be at the same level of abstraction.
  • All public methods inside a class should be at the same level of abstraction.
  • All classes should be inside a package/namespace.
  • All sibling packages/namespace should be inside a parent package/namespace.

Sandro Mancuso, Balanced Abstraction Principle, https://codurance.com/2015/01/27/balanced-abstraction-principle/.

Let's see how it relates to a little previous example. In the following snippet, the Save method is not at the same level of abstraction:

public class Car{
  public int CurrentMileage(){...}
  public void TravelTo(Location location){...}
  public void Save...