Classic OOP in Python
Laura Creighton
lac at openend.se
Wed Jun 17 18:22:35 EDT 2015
In a message of Wed, 17 Jun 2015 14:33:43 -0700, sohcahtoa82 at gmail.com writes:
>I had a Java class where we had to learn TDD, and that's the way TDD
>was taught to us, and I hated it. We watched a video of this guy
>explaining TDD with a hat that was red on the front and green on the
>back. It involved writing a simple failing unit test, then write
>code to fix it, then refactor the tests and/or code. As an in-class
>exercise, we had to write an implementation of Conway's Game of Life.
>I threw TDD out the window and just wrote the damn program in under
>15 minutes, then another 10 minutes to write unit tests that tested
>every possible code branch and several invalid inputs. Meanwhile,
>the people doing TDD the "right" way didn't even have a complete
>program after over an hour. The brand of TTD we were taught would
>end up multiplying development time by at least a factor of 3, and by
>the time you were done, at least 75% of the tests you had written
>will have been removed due to rampant refactoring. IMO, that kind of
>TTD is an utter waste of time.
I'd hate that too. But that's not the TDD I know, or teach. Please
don't write off TDD as a result of this experience.
Laura
More information about the Python-list
mailing list