If you make a code change that breaks one test and think it might be a broken test, it’s easier to read that test if it’s not dry. Because all of the dependencies are listed out more explicitly.

Dry tests use a lot of helper methods and those are a layer of indirection. To understand a dry test, you have to also understand the helper methods, and whatever helpers they all call.

> Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.