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

Code Smells

Code smells are more granular smells that are usually easier and less costly to fix than design smells. There are four categories of code smells:

Bloaters

Something that has grown so large that it cannot be effectively handled:

  • Long Method: Methods should do only one thing. Single Responsibility Principle (SRP) violation. One level of abstraction. "Keep all entities small" object calisthenics rule violation.
  • Large Class: Classes should have only one responsibility. Possible SRP violation. No more than 50 lines per class. "Keep all entities small" object calisthenics rule violation.
  • Primitive Obsession: Don't use primitive types as substitutes for classes. If the data type is sufficiently complex, use a class to represent it. "Wrap all primitives and strings" object calisthenics rule violation.
  • Long Parameter List: "Keep all entities small" object calisthenics rule violation.

Ideal: 0...