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


Cohesion (noun): When the members of a group or society are united.

Cohesive (adjective): United and working together effectively.


Cambridge Dictionary:

Cohesion is a measure of how strongly related and focused the various responsibilities of a software module are, and it "refers to the degree to which the elements of a module belong together."

Cohesion is everywhere, not just in code. For example, companies try to create highly cohesive teams, with cross-functional roles (developers, business analysts, designers, and so forth) that work closely together to achieve a specific goal, such as a software product update.

A component should implement a single behavior or responsibility, and all the parts of the component should contribute to the implementation of it. Components should only be created if all parts they group are collaborating together to implement a behavior...