CSC 216 Lecture Notes - Lecture 23: Github, Team Dynamics, Whiteboard
Document Summary
We, as computer scientists, almost never work alone. Complex software is way too large to be completed by yourself! If it is(cid:374)"t, the(cid:374) (cid:455)ou"(cid:396)e (cid:373)issi(cid:374)g se(cid:272)u(cid:396)it(cid:455), p(cid:396)i(cid:448)a(cid:272)(cid:455), a(cid:374)d safet(cid:455) (cid:396)e(cid:395)ui(cid:396)e(cid:373)e(cid:374)ts! When you work with other programmers, you should set up certain ground rules. This makes sure that everyone gets a fair share of work, and that everyone understands the code that other people have added themselves. Have everyone get together to define the ground rules as a team. The ground rules can change as team dynamics change- ie, losing people with a certain level of experience and gaining people with more/less experiencel. For project 3, define your ground rules in the wiki: the teaching staff can refer to yoru ground rules if we need to handle a dispute. Task planning is the technique of breaking down a large project into smaller subsections, then dividing those subsections into tasks.
