Yahoo Answers is shutting down on May 4th, 2021 (Eastern Time) and beginning April 20th, 2021 (Eastern Time) the Yahoo Answers website will be in read-only mode. There will be no changes to other Yahoo properties or services, or your Yahoo account. You can find more information about the Yahoo Answers shutdown and how to download your data on this help page.

Trending News

Promoted
nate h
nate h asked in Computers & InternetProgramming & Design · 10 years ago

Question about programming project?

I'm working on a programming project with another person overseas. What kind of programs should we be looking at so that we can easily update and change code without having to send completely new files to each other? Would something like a VirtualBox on Ubuntu be a good idea? Help.. I've never worked on a project like this before!

Thanks

Update:

In other words.. this is a collaboration project and I don't know where to start =P

Update 2:

Thanks a lot for the suggestion. ClearCase and etc was exactly what I was looking for.

Any other tips on how to effectively do a collaboration project?

2 Answers

Relevance
  • Nick T
    Lv 7
    10 years ago
    Favorite Answer

    Not sure how or why you would want to use Virtual Box?

    You should use some form of configuration control program that supports WAN shares (clearcase, cvs etc) or at the very minimum make use programmers compare tool (WinMerge, BeyondCompare etc) to minimise the files that have to be shared around.

  • ratter_of_the_shire
    Lv 7
    10 years ago

    Depending on the scope of the program submitting patch files against versions can work perfectly well. I believe you can just use diff to pull out a patch file against a known version file.

    Get a initiial version, then divide up tasks for the next week or two, then resolve the patches to get the next version, repeat.

    Also if you use networked storage (something you can both access) can help, so long as you both agree only to upload changes in the form of a patch file or as a new version, however don't substitute this for frequent and proper communication. You should both know what the other is currently working on and the goal or rationale behind it.

    You can use a version management system like subversion, but there is some overhead in setup and maintenance so it may not be worth it.

    Also you should choose right now who is going to be the technical lead. Put the egos aside and keep the goal in mind. Having a single technical lead will just save time overall when there is a deadlocked disagreement about implementing the technical features.

Still have questions? Get your answers by asking now.