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


Fizz Buzz by cyber-dojo

Cyber-dojo foundation (See license):

Write a function that takes numbers from 1 to 100 and outputs them as a string, but for multiples of 3, it returns Fizz instead of the number, and for multiples of 5, it returns Buzz. For numbers that are multiples of both 3 and 5, it returns FizzBuzz.


Start by writing a failing test. Think about what behaviors your code should implement.

Fizz Buzz – partial walkthrough

Let's first pick the behavior where numbers not divisible by 3 or 5 are returned as a string. Let's start with number 1.

Write a new failing test.

When I fizzbuzz number 1, I get back a string representing it

Use fake it as an implementation strategy.

return "1"

Run the test and make sure it's green.

Write a new failing test since we do not have enough examples to prove the behavior we are implementing yet.

When I fizzbuzz number 2, I get back a string...