Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!news.kei.com!newsfeed.internetmci.com!vixen.cso.uiuc.edu!howland.reston.ans.net!torn!nott!cunews!tina.mrco.carleton.ca!knight
From: knight@mrco.carleton.ca (Alan Knight)
Subject: Re: Source code/Repository management
X-Nntp-Posting-Host: tina.mrco.carleton.ca
Message-ID: <knight.820278382@tina.mrco.carleton.ca>
Sender: news@cunews.carleton.ca (News Administrator)
Reply-To: knight@mrco.carleton.ca (Alan Knight)
Organization: The Object People
References: <DKD879.J5L@ritz.mordor.com>
Date: Fri, 29 Dec 1995 23:06:22 GMT
Lines: 21

In <DKD879.J5L@ritz.mordor.com> jpletzke@ritz.mordor.com (Jonathan Pletzke) writes:
>I have done this in C/C++, but have encountered resistance from 
>Smalltalkers who would prefer to trade file-ins, ad-hoc test items, 
>object files (BOSS or ObjectFiler), or an entire image.  I believe that 
>this is due in part to the personal nature of Smalltalk develpment, but 
>find that it can be counter productive to delivering quality code.

Gack! Programmers often tend to be opposed to unnecessary frills like
testing, documentation, and version control, but they're certainly
essential to delivering quality code on any decent-sized project. You
should check into one of the commercially available team programming
tools like Envy (my personal preference) or Team/V. I would be very
reluctant to start a large project without such a system in place.


-- 
 Alan Knight                | The Object People
 knight@acm.org             | Smalltalk and OO Training and Consulting
 alan@objectpeople.on.ca    | 509-885 Meadowlands Dr.
 +1 613 225 8812            | Ottawa, Canada, K2C 3N2

