-- Shakespeare, Love's Labour's Lost
I was inspired a while back by the talk "Write the Other Half of Your Program" by Jason Hemann and Daniel Friedman.
What would an example of this look like? Let us look at one example with the FizzBuzz kata.
We see in the code above that the conditional statements around when to Fizz, Buzz, FizzBuzz, or just return the value given are more complex than they normally are.
Here is the Fizz condition:
(and(fizz? x)(not-buzz? x))
We see that in the Fizz condition we are testing that it is a Fizz and that it is not a Buzz, this will allow us to relocate the this condition before the FizzBuzz condition if we want to, but only if the FizzBuzz condition will allow this (which it will).
Here is the Buzz condition:
(and(buzz? x)(not-fizz? x))
We see that it is the reverse of the Fizz.
Here is the FizzBuzz condition:
(and(buzz? x)(fizz? x))
We see that we are testing for both Fizz and Buzz conditions.
Finally here the else condition:
(and(not-fizz? x)(not-buzz? x))
We see that we are looking for Not Fizz and Not Buzz. In a sense we have came up with our own little DSL around the logic of FizzBuzz and at the same time have written our conditions in such a way as to allow for them to be completely rearranged!