October 26, 2001
Categories:
Articles
One of the most common raps against XP isn’t even true. People think we say that documentation is a bad idea. XP is focused on conversation for maximum effectiveness. Our recommendations on documentation follow from that simple fact.
October 21, 2001
Categories:
Classics
Test everything; eliminate duplication; express all ideas; minimize entities:These few simple rules, applied locally, can help a high quality global design to emerge.
October 8, 2001
Categories:
Articles
One of the most common failings of XP teams is insufficient testing. XP asks for more testing than many teams are used to. But what about projects that need reliability at a substantially higher level? Are they out of luck?
October 7, 2001
Categories:
Classics
Kent Beck has described XP as designed to go with people’s natural instincts. In this short series of articles, we’ll take a look at how XP accomplishes goals without a need for lots of discipline or management pressure. In this article, the topic is documentation.
At the Agile Developer Skills course at the Raikes School, I commented that we don’t usually test accessors. But we test everything. Is this a contradiction?
My critiXXXXX advisors expected a more function-oriented solution. Here’s something a bit better, perhaps …
I’ve been working with Scala a bit, just to learn what it is. I’ve found it interesting, if frustrating. Here is a bowling experiment.