I know, i know... mea culpa. I'm quick to blame others of miscommunication but i'm the worst offender.
What i was trying to explain is that source control isn't a replacement for team communications. If you often find yourself fighting for control of the same file with one or more other developers then you need to look at root causes - no software out there can help you until you do. My example was a little light hearted: of course i don't expect people to check every action on every file with every other developer as and when they need access to that file. Rather, i would hope that code has a modicum of logical structure into modules of some kind, and that developers can plan their tasks ahead of time in enough detail to know which modules they will be accessing. It's less a case of "hands off file x" and more a matter of "i need to change something in the database access layer. bob said he was working in there today. i'd better ask him first". If you continuously find yourself having problems with multiple developers overwriting each other's changes, then you need to apply some structure before you can apply some software. my apologies for any misunderstanding. /t >-----Original Message----- >From: Sean Corfield [mailto:[EMAIL PROTECTED] >Sent: Thursday, April 14, 2005 7:54 PM >To: CF-Talk >Subject: Re: What's your setup for multiple developers > >On 4/14/05, RADEMAKERS Tanguy <[EMAIL PROTECTED]> wrote: >> >That's basically how we've worked except for the source >> >control. The "hey bob" part just doesn't work though. >> >> How many developers do you have? Tens? Hundreds? >> >> a) If you can't coordinate work between multiple developers then you >> have bigger problems than version control. To wit: > >Claiming that a team is dysfunctional because they don't ask each >other every single time they want to edit a file is ridiculous! > >If developers are being productive, working through bugbase issues, >they're going to be touching a lot of files in the course of a day. >Having them physically ask everyone for every single file is just >silly! All that noise and that many interruptions?? > >Your "hey bob" idea would only work for a very small number of >developers who all sit in one room, close enough to each other that >they could overhear everything that is said. And assumes that if >they're deeply involved trying to figure out a bug, they don't mind >someone interrrupting them every few minutes asking if they're editing >some file... >-- >Sean A Corfield -- http://corfield.org/ >Team Fusebox -- http://fusebox.org/ >Got Gmail? -- I have 50, yes 50, invites to give away! > >"If you're not annoying somebody, you're not really alive." >-- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:202809 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
