[sarettah]

Originally posted by RyanLanane@Mar 23 2005, 09:53 PM
Shot back at you again

I look at stubborn and confrontational as almost the same thing in this instance. For example you both have your half of the program complete and the two pieces aren't fitting together.

In my past experience with programmers (when I had multiple programmers working on a job, or someone editing a prior programmers work) it is never either of the programmers fault. They are both stubborn about the possibility they could have made a mistake, which leads to confrontation when I had to go tell both of them the other one says the problem is with their work.

And yeah I tried "I don't care what's wrong, just work together and fix it guys" Maybe you aren't like that, but a lot of people I have dealt with were.... Always a bad apple or two in the bunch though

Like I say, a good solid project leader should have nipped that in the bud early on. If the project is speced properly then putting it together is a cakewalk...

Most time on a project should be spent in the design phase and the testing phase, not in the coding phase...

But, multiple programmer projects can be difficult to put together. I have tunred down many projects because of the reluctance of the non programmer folks I was dealing with to appoint someone other than themselves to be in charge. A multi programmer project without a clear lead programmer to keep his/her thumb down on the team is usually a straight death march (which is a great book on project management, etc... funnier than all out to read too...oh, the book is called "Death March"...)



hmmm...still waiting for HellPuppy to weigh in on this thread. He has some very definite opinions on this subject....