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.
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.