This is why I don't get along well working with other programmers. If someone else comes up with a better way of doing something than I did, more power to them. But if my way is better I stick to my guns. The best way I've found to work with someone else is to take control of one aspect of the project, let the other person/s deal with other parts, and stay out of each other's way unless their part causes a problem or vice versa.
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. So keep that in mind in your case, if you want to do well in class then you're probably best to keep your mouth shut and be seen as a "team player" no matter how much the code sucks. It's stupid, I don't agree with it, but that's the way it is in my experience.
|