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

Should I Use Classic TDD or Outside-In TDD?

Both. They are two different approaches, and different situations require different strategies. The question is not "should I use classic TDD or Outside-In TDD?", but rather "when should I use classic TDD and when should I use Outside-In TDD?"

When our knowledge of the problem/domain is not very high, classic TDD is a great way to discover/explore solutions. If you are a beginner, classic TDD is a lot more accessible, since you don't have to take design decisions without feedback. Outside-In TDD requires a deeper knowledge of design since we don't get the feedback loop of the mess, but it can be a lot more efficient and focused on the business. In the end, context is king, and we should use the most appropriate technique required by the context.