Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Agile Technical Practices Distilled
  • Table Of Contents Toc
Agile Technical Practices Distilled

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
4 (6)
close
close
Agile Technical Practices Distilled

Agile Technical Practices Distilled

4 (6)
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)
close
close
Lock Free Chapter
1
Section 1
7
Section 2
13
Section 3
19
Section 4
25
Chapter 21
28
License: CyberDojo

Katas

Connecting Code Smells with Cohesion/Coupling

In the following table, we have grouped code smells in relation to coupling or cohesion excesses. Because cohesion and coupling are more abstract concepts, we can make use of code smells to help us detect imbalances.

For each row in the Degree column and in the Cohesion/Coupling column, highlight the correct concept and then add a reason in the reason column. After the table, we have listed several sample reasons to use. In some cases, both coupling and cohesion apply.

Figure 11.5: Connecting code smells with cohesion/coupling

Note

For answers, see the Appendices section on the page 388.

Some ideas for the Reason column

  • The method is probably doing too much.
  • The class is probably doing too much.
  • A class knows too much about non-immediate neighbors.
  • The class just delegates behavior and has no behavior or state.
  • The class hierarchy is probably wrong.
  • The class misses...
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Agile Technical Practices Distilled
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon