working with a team of programmers
Author
I have some questions about what it is like to work with other people on the same project.
I have worked with a friend of mine on a couple programs. What we did is just copy and paste each other''s code when one of us had completed a feature.
How is this handled in real software companies?
Also, what does it mean to "commit?"
In companies they usually use things like CVS or Sourcesafe. These ''programs'' allow multiple people to work on the same document. Once a person is done with the code he/she commits it (I thought it was something like that) to the database.
This way you can keep different versions of your files. So if someone screws up, you can go back to an earlier version. Well, that''s the basics. More info on www.cvshome.org.
This way you can keep different versions of your files. So if someone screws up, you can go back to an earlier version. Well, that''s the basics. More info on www.cvshome.org.
It depends on the size of the project you are working on. For example, where I work we actually have four different products and 2/3 programmers, so we tend to be working on different things.
The projects are quite large so even when we work on the same project, we work on different parts of the project. Sometimes we need to work on the same files but we just have to wait until the files are free (we use SourceSafe).
"Absorb what is useful, reject what is useless, and add what is specifically your own." - Lee Jun Fan
The projects are quite large so even when we work on the same project, we work on different parts of the project. Sometimes we need to work on the same files but we just have to wait until the files are free (we use SourceSafe).
"Absorb what is useful, reject what is useless, and add what is specifically your own." - Lee Jun Fan
Agree with the above two posts. Would add:
Different programmers on a project tend to specialise. For example on a game, one guy might do the engine/graphics stuff, another might do the AI, another the tools, another the physics etc.
So although there''s lots of code that has to work together, the actual source files and areas are separate. Each guy works on their own area, and as soon as they''re sure their code is stable the "check it in" to Source Safe/CVS/AlienBrain etc.
Different programmers on a project tend to specialise. For example on a game, one guy might do the engine/graphics stuff, another might do the AI, another the tools, another the physics etc.
So although there''s lots of code that has to work together, the actual source files and areas are separate. Each guy works on their own area, and as soon as they''re sure their code is stable the "check it in" to Source Safe/CVS/AlienBrain etc.
Also, when people work on different parts of the same project a lot on consideration has to made as to making sure it all works together. For example, my last project, I had to write classes to an EXACT interface specification, so that when the guy who had written the other bit of the program delivered all of his function calls matched all of my prototypes perfectly. I believe good documentation is key to working on a project with other people. It compiled first time too...
- CheeseMonger
- CheeseMonger
I tried an e-mail project. Big failure. Haven''t heard from the guy in 3 months.
Scott Simontis
Big Joke: C#
Scott Simontis
Big Joke: C#
Author
quote:Original post by Village Specialton
I tried an e-mail project. Big failure. Haven''t heard from the guy in 3 months.
Sorry to hear that, but LOL. Did email work well as a means of communication?
Proceeding on a brutal rampage is the obvious choice.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
