🔒 Locked

Team Programming

Started by Spintwo Jul 9, 2004 at 7:33 AM 3 replies 1.1k views

Original Post

Jul 9, 2004 at 7:33 AM

When programming with a group or team, how do you like to split things up? Having on person start, then passing it on to the next guy to write the next bit of code sounds tedious. How do you arrange stuff so that all team member's things are compatible with each other?

Scrime

Jul 9, 2004 at 7:50 AM

Generally, you have an overview of the project layout before you begin. Planning before coding becomes even more important when working in a group.

As far as working on the source code at the same time, thats just what source control solutions are designed for. People working on the code "check out" the files that they are working on, make their changes, and then "check" then back into a central repository. If more than one person is working on a particular source file at a time, then they will have to merge their changes (which can sometimes be handled automatically), before commiting it to the central repositiory. CVS, Subversion, VSS, and Alienbrain are all examples of versioning control systems.

Planning, source control, and good communication between team members are key to working on a programming team.

Spintwo

Jul 9, 2004 at 2:38 PM

Will those programs work over the internet?

T1mb0

Jul 9, 2004 at 2:44 PM

Yes, at least CVS and subversion do. (didnt use others so far)

antareus

Jul 9, 2004 at 5:20 PM

You'll want a design that lends itself to separate modules. Agree upon interfaces to communicate between the modules. Couple this with a source control system, a wiki, and constant communication and you have a start. :)

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.