|
Re: What Makes A Good Leader?
We had a freshman do all of the programming this year. He did it, but was pretty well fried at the end.
The last thing you should do is "hog the code" because if two or three programmers can be effectively coordinated it will spread out the workload and keep fresh eyes looking at the code. Your "OCD" about neat programming could actually be a strength in this regard: if every programmer who works on the code works in the same general format of tabs and spacing etc they will more easily be able to read and comprehend each others code and therefore be a more effective team. Heck, even if you go through after every revision and neaten up the code to a uniform format you would probably be helping things.
If you could handle coordinating 2 other programmers, collectively developing a programming format that works for all of you, and be willing to compromise on programming styles I think you could do okay. Also remember that a good leader is humble, flexible, and usually has a non-abrasive personality.
__________________
Theory is a nice place, I'd like to go there one day, I hear everything works there.
Maturity is knowing you were an idiot, common sense is trying to not be an idiot, wisdom is knowing that you will still be an idiot.
|