Quote:
|
Originally Posted by irseg
I found that in a college environment, documenting your work and working harmoniously in a team is considered far more important than producing good code.
|
wish i went to your school. all you get at mine for working harmoniously and producing bad code is bad grades all around.
Rekna, some people are just sensitive and while likely you were right to change the code perhaps you could have been diplomatic about it? Let him know you think there is a better way to accomplish something or you found a bug, and let him implement the solution. This way he has ownership of the solution as well and hopefully will believe in it as well.
Part of group programming assignments is learning to work as a group. I am fortunate right now to work with a team of programmers who all get along well, all communicate well. We get called into each other's office to look over code, take breaks to discuss things, and recognize each others' and our own strengths and weaknesses. In fact, if we get our way we will be taking over an unused conference room as a group office.
we each have our assignments and projects, but we understand the goal and recognize we are on the same team. the sales people who make promises for us to keep and frequently change requirements are the other team.
