--- In [EMAIL PROTECTED], Steve Berczuk
<[EMAIL PROTECTED]> wrote:
> On Thu, 30 Dec 2004 13:47:23 -0500, Ron Jeffries
> <[EMAIL PROTECTED]> wrote:
> >
> > On Thursday, December 30, 2004, at 12:45:15 PM, Jason Yip wrote:
> > > I also have an assumption about staging the "safety nets", if you
> > > will. Immediate group of unit tests for the current feature should
> > > run in at most 2 seconds, pre-commit (aka Private Sandbox) build
> > > should be < 5 minutes (ideally less than two), post-commit full
build
> > > falls into the Ten Minute Build (at most) practice. There may
be more
> > > staging depending on how complicated the deployment environment is.
> >
> > > Every time there is a failure, we learn to add something to the
> > > previous faster-running stage.
> >
> > If it works, do it. And write it up.
>
> This is basically the idea behind the dependency structure in the SCM
> pattern language between Private System Builds, Integration Builds,
> and the various kinds of tests.
>
> http://www.scmpatterns.com/book/pattern-summary.html
The SCM patterns book definitely help me clarify my thoughts on this
structure.
...
> There is a story in one of Gerry Weinberg's books (Psychology of
> Computer Programming?) where some programmers lamented the rise of
> Time Sharing Terminals because they would lose the chance to discuss
> their work w colleagues while in line for the card punch machine...
> This reminded me a bit of that... ;)
XP 2nd Edition has a similar comment about "the inherent reflection
time build into the synchronous style". My first thought was, if
reflection is important, why do I need an excuse to take time to do it?
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/