When taught TDD, especially at the beginning of our journey, we’ve all faced the question: “Why is this so dumb?“.
More frequently than what one would want, we are forced to write silly code, fake implementations, or just “the minimum code required”.
On the other hand, there are times when we have an algorithm formed in our minds, and we are so sure about it, we end up skipping tests.
The Transformation Priority Premise (or TPP) is an effort for a formalization to guide test-driven developers into choosing the best next test and the best possible implementation at that particular moment.
By going through a few examples, we will see the evolution of code, and how a decision can make our solution go in a completely different way.
We will see that the “minimum code required” is not as random and silly as we first thought, and that there is a proposed structured approach we can follow.
The format: A 40-minute guided hands-on workshop followed by a Q&A session
YOU MAY ALSO LIKE: