Skip to content

Latest commit

 

History

History
43 lines (26 loc) · 3.04 KB

communicating-and-collaborating.md

File metadata and controls

43 lines (26 loc) · 3.04 KB

Class Tools for Communicating and Collaborating

We will be communicating with each other and collaborating extensively throughout Access Code. To keep things efficient, we have set up some systems for you to use for communicating with each other and with instructors and TAs. Access Code is meant to prepare you for a career in tech, and that includes using all the cool tools that professional developers use. All the tools we will be using in this course are used extensively by professional developers, and we also think they're great!

Communications

We will primarily use Slack for communicating with each other. Slack is at heart a chat application, but all conversations are archived and searchable so you can always go back and revisit helpful conversations. Slack is used at many major tech companies (you know the names), so we've decided to do the same.

We'll set up Slack together and discuss how we'll use it throughout the course. We recommend downloading the Android or iOS Slack app to keep up to date when you're not at your computer.

We will be sending important announcements through Slack, so please don't hesitate to get in touch with ay of the Access Code staff if you're having issues with it.

Work assignment, submission and review

Assignments will be posted on Github in the appropriate repo for that course unit. The most recent assignment will appear at the top of the README.md, and the corresponding materials for the assignment will be added to the repo in a directory just for that assignment.

You will submit assignments via Github as follows. The process may be confusing at first, but bear with it and it'll become second nature.

  1. Clone the current unit's repo
  2. Checkout a new branch (git checkout -b branch-name)
  3. Complete the assignment (easier said than done, eh?)
  4. Stage and commit your changes (git add -A . then git commit -m "completed assignment with fortitude and flair")
  5. Submit a pull request on that unit's repo with your completed assignment. Check out Github's pull request help page if you have any issues.
  6. Do a little dance!

Instructors and TAs will review your work and give comments on your pull request directly. Once reviewed, they will close the pull request. This doesn't mean you did anything wrong, it simply means your work was reviewed.

Pair and group work

For pair and group projects, students will create a shared repo on Github for each project. Instructors and TAs can view their code at any time, and give feedback when appropriate.

Pair programming

We will be pair programming most of the time. Pairs of students take turns "driving."

Pairing format:

  1. Student 1 "drives" on his/her computer while student 2 assists
  2. After exercise / 30min / 1hr, student 1 commits and pushes his/her changes
  3. Pair switch to student 2's computer
  4. Student 2 pulls the most recent changes, and keeps working
  5. Repeat!