On Tue, Mar 2, 2010 at 8:36 PM, Nic Benders <[email protected]> wrote:
> Either I don't understand the meaning here, or I completely disagree. How much experience do you have with TDD and Continuous Integration? CI doesn't mean you have a test server (such as CruiseControl). That's just a stopgap measure if your total test run gets too slow. If two people are working on the same code, they are each other's test server. This is how TDD and CI got bootstrapped, back in the days before "Agile". And if you continuously branch and merge, then what's the point? You are just And, as usual, Agile has the default check. If you do it my way, your process cannot fail silently. You will know when to add more layers to your system. But the other way around - adding the layers first - makes them impossible to remove, and makes their drag hard to notice. I just got off a shift wasting time repairing the build because one guy on the team was not practicing CI, so I'm a little irritated at the topic now! -- Phlip http://c2.com/cgi/wiki?ZeekLand -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
