Slashdot Mirror
Guide For Small Team Programming?
dm writes "I run a small design shop and have been doing more and more web development, including fairly involved back-end programming of what's now essentially become our own CMS. Up to now I've been doing all the programming myself. Now we are working with a second programmer for the first time. I already use version control (SVN) and an issue-tracking system, and I guess we are both decent at what we do — although self-taught, but we both lack experience programming in a team context. Is there a useful guide for this? Most of the tutorials I have seen for Subversion are surprisingly organized from a single coder's perspective. Where else should I look?"
I assume you're the boss, so you could work 9am-5pm and he could work 5.30pm-1.30am.
That way you can still code naked.
The optimal programmer team size is 1.
Google Code uses SVN.
Subversion wins, fatality.
Wanna fight ? Bend over, stick your head up your ass, and fight for air.
Mom?
Oops. That should be "unit tests", not "nit tests". I definitely don't recommend checking your fellow programmer for louse eggs. Unless you're both chimpanzees. Then it would be fine.
To: coders@example.com
Subject: Working on main.c, leave it the frig alone until further notice. EOM.
Problem solved :D
How are sites slashdotted when nobody reads TFAs?
Bathe frequently.
Floss, Brush & Mouthwash.
Wash hands after bathroom use.
There is an even finer line between good and bad analogies.
You just have do draw a line somewhere. I for one always have some garlic, a crucifix and a wooden stake in the glove compartment, even though it's quite possible I'll never need them.
You don't and I'm not gonna hold it against you. I'm not even going to say your car isn't properly equipped.