Re: OOP/OOD Philosophy

Robert C. Martin wrote:

> Does it? Oh I agree that there are some over-enthusiastic blurbs
> written here and there. But where are the serious articles and books
> that treat XP as a discipline that has no problems? Certainly the
> primary XP books don't fall into that category.

Strong the Dark Side Is

TDD's force can cause problems. Used alone, without checks and balances from
code reviews and feature reviews, frequent testing can help add many useless
features, providing a very high apparent velocity. Used incompletely, with
huge gaps between tests, TDD can reinforce bad code.

Some folks write a few tests, then write code and "refactor" for a long
time, without frequent testing. These behaviors add back the problems that
TDD helps a healthy process avoid.

TDD applies our Agile "headlights metaphor" in miniature. Imagine headlights
that can only strobe, not shine continuously. Each time you hit the test
button, you get a glimpse of your implementation's road ahead. So to change
direction, you must test more often, not less.

Teach your colleagues to write tests on code you understand, and learn to
write tests they understand. This learning begins as a team collaborates, at
project launch time, to install and use a testing framework.

--
Phlip
http://www.c2.com/cgi/wiki?ZeekLand



.