Tdd like beethoven
Download as PPTX, PDF1 like479 views
This document discusses how test-driven development (TDD) is similar to Beethoven's compositional process. It outlines constraints for practicing TDD like Beethoven, which include not compiling or running code, using only a text editor, and not using autocomplete. The process involves writing a failing test, adding code to pass the test, refactoring code while ensuring tests still pass, and repeating until the problem is solved before finally compiling and running the code.
Tdd like beethoven
- 1. TDD like Beethoven José E. Rodríguez Huerta (@jrhuerta)
- 3. @jrhuerta
- 4. The Constraints Get a small problem you want to solve in code You can use all the documentation you need You can use a text editor with syntax highlighting, but… @jrhuerta
- 5. The Constraints Do not compile or run the solution! Do not use auto-complete! @jrhuerta
- 7. “composing” Come up with a test and write it down in the text editor. Reason about why it must fail right now. @jrhuerta
- 8. “composing” Write down the code that will make the test green. Explain to yourself why it will make the test pass. Double check for syntax errors, exceptions... @jrhuerta
- 9. “composing” Refactor the code. Explain to yourself/PARTNER why the refactoring is better. Explain why all the tests still pass. Double check for syntax errors, exceptions, ... @jrhuerta
- 12. GRAND OPENING Compile and run Change the code so it runs and compiles Write down all the changes you had to make @jrhuerta
- 13. Powerful Questions How did it feel? Why was it different? How is it going to help you? @jrhuerta
- 14. THANK YOU for PARTICIPATING! and to David Tanzer for the original idea! @jrhuerta