On Friday, December 31, 2004, at 5:38:52 PM, Jason Yip wrote:
> --- In [EMAIL PROTECTED], Steve Berczuk
> <[EMAIL PROTECTED]> wrote:
>> On Fri, 31 Dec 2004 14:38:27 -0500, Ron Jeffries
>> <[EMAIL PROTECTED]> wrote:
>> >
>> > On Friday, December 31, 2004, at 1:34:12 PM, Jason Yip wrote:
>> > > - When a build breaks, it's an opportunity for us to learn how to
>> > > improve our build, tests, and deployment process.
>> >
>> > Well, except that no one's there.
>> I'm not understanding this...
> Neither am I... *Everyone* is there to witness the build failure.
No ... "Everyone" is somewhere else, both physically and mentally,
coding away. A failed build interrupts everyone, or everyone
implicated, at their desk. But the whole theory of your idea is that
they have moved on. No one is ready, no one is engaged in the build
process. It's a fire alarm.
It also seems a bit nose to the grindstone, now that I think about
it.
I don't know, I've never tried it. It might be wonderful. But it's
not where I'd start. It might be where I'd wind up.
Ron Jeffries
www.XProgramming.com
The central "e" in "Jeffries" is silent ... and invisible.
Don't you wish he was?
(See www.xprogramming.com/xpmag/jatasyouwere.htm
for a discussion of the subjunctive mood as used above)
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
