Heh, I feel so much more comfortable arguing against the conventional wisdom (as do most Mac and WebObjects users probably), but in this case, I've got to support the conventional wisdom where it recommends Source Code Management (SCM). For any commercial project, I feel exposed without a couple things in place: a good SCM system that supports concurrent development among team members and a solid, web based issue tracking system. Other things come to mind, like a good IDE, a good programming language, a good set of frameworks, a good development team, (a Mac!) and so forth, but whether working in a team or working on my own, I've too often been supported by CVS (which is arguably not even a "good" SCM at this point) to support any arguments for developing without SCM. It provides convenient incremental backup for the code allowing any loss, for whatever reason, to be conveniently restored. It allows reviewing the changes that went into any release It provides logs to summarize the history of changes It allows concurrent development without team members stepping on each other's toes too often. It provides a convenient means for new team members to obtain the latest working version of the code (or any other version, for that matter). It provides a clear record of who made which changes. I really feel that SCM and good architecture are orthogonal. I worked with a company that produced a large number of successful, maintainable systems in a timely, budget conscious fashion. All of them were developed using CVS. They're moving to Subversion. There may be better SCM tools out there than either Subversion or CVS, but SCM should be in place for any team that's developing commercially. Regards, Jerry On Mar 13, 2006, at 6:30 AM, Mike Schrag wrote: Just to leave no religious debate undebated :) I'm going to have to respectfully disagree on this one ... CVS, for example, certainly has its issues, but it takes 5 minutes to get it running, there's near zero administration for it, and it has really nice support built into Eclipse. If you use extssh to connect to it, all you have to really do is cvs init a folder and you're done. With eclipse you never have to touch the commandline again. The benefits and convenience of having it running are SO worth the minimal effort to get started, in my opinion. Even on personal projects I use my own repository. You can certainly get by without SCS -- plenty of people do -- but, man, why would you do that to yourself? This is just one of those technologies that makes my life easier (and SAFER). I can't imagine not having one in place at this point. -- __ Jerry W. Walker, WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems 203 278-4085 office |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com