From: "Debaun, Steve [Seminis/2400]" Date: 2006-05-12T06:26:15+09:00 Subject: Re: Sharp knives and glue Having not experienced large-scale development farms firsthand, wouldn't this just be a matter of proper unit tests? 'its not my code, my unit tests work fine'. sd -----Original Message----- From: John Gabriele [mailto:jmg3000@gmail.com] Sent: Thursday, May 11, 2006 2:04 PM To: ruby-talk@ruby-lang.org Subject: Re: Sharp knives and glue On 5/11/06, rob wrote: > Re-opening classes is one of the things that makes ruby great. [snip] > > Why so precious? If you don't want people to modify your code say so. > If they go ahead and it blows up it's their fault. Not to take any sides, but I think I've heard the argument go: if you're working on a team on a large project, and all of a sudden "your" class breaks, management doesn't want to hear about someone else opening your class... they'll just see your name on the class causing the hold-up and then it *becomes* your problem. (snip rest)