At 9:22 AM +0000 2/19/02, Piers Cawley wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
>> The first person to say "But XP says code first!" will be summarily
>> mocked, as that's completely full of crap. You have been warned. :)
>
>Actually, XP says tests/interface first and be prepared to change it
>if the code tells you to.
That, then, would be a good reason to mock them. :)
>But XP is specifically about small teams working in close physical
>proximity on an application that is, in some sense 'complete':
>ie. interfaces generally don't have to be published. Which doesn't
>really sound like Parrot anyway.
Yeah, compilers (and OSes, and other big projects) don't seem to fit
the XP mold in many ways. XP looks good for projects equivalent to
building a house. Projects akin to bridges, large buildings (like,
say, cathedrals...), or modern CPUs are in a different class.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
