[Yact-dev] Extreme Programming

[Daniel B. <ba...@we...>]

Hi all,

I just read the book Extreme Programming by Kent Beck (I just love him),
and it struck me how close that is to open source development.
Everything is tested all the time since so many people are using it, all
development is used in very short iterations since nobody has very much
time to work on it anyway, integrations are done often since everybody
works against the same cvs server, redesigning and rewriting often since
we don't like to look at bad code, and most importantly, everything is
developed in order of importance (at least to somebody) since everybody
just implements the things that means most to him or her.

I hope we can use something as close to this as possible for the Yact/Qb
pair, just implementing the features we want the most, letting the need
from Yact pull the development of Qb.  

I'm not just suffering from the "when your latest tool is a hammer, all
problems look like nails" syndrome, am I?

/Basic