Skip to content

Instantly share code, notes, and snippets.

@cgeglio
Forked from damwhit/mod_0_session_3_readings.md
Last active September 10, 2019 04:08
Show Gist options
  • Save cgeglio/40b06fad759c4a83835e4115bfec66e3 to your computer and use it in GitHub Desktop.
Save cgeglio/40b06fad759c4a83835e4115bfec66e3 to your computer and use it in GitHub Desktop.
Mod 0 Session 3 Readings and Responses

Session 3 Readings and Responses

The readings and responses listed here should take you approximately 50 minutes total.

To start this assignment:

  1. Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
  2. Click the Edit button when you're ready to start adding your answers.
  3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Assignment 1 (20 min)

Read David's article on Git and GitHub

  • Use the article and outside resources (Google!) to describe the general process of a collaborative git workflow in the space below.

If you are working on a collaborative project, you can use GitHub to make sure all of your teammates are working on the most current version of the project.

If you are working on a project by yourself and find yourself at a good stopping point, you would commit all the changes from that session and then push those changes to your repository on GitHub. Things are a little more complicated when you have a team project because multiple people could be simultaneously making changes to the same code. By creating a branch, you can basically create a safe space to work and try things out before fully commiting to the project repository. You'll still be making commits, but just to the branch, not the repo. While working on a branch, you can open a pull request which will open up your commits to discussion. Your teammates can then offer feedback on the branch you are working on. From there, you can edit your branch based on the comments you have received. After that, you can deploy from your branch to test out how it will work. The last step, once your branch has been verified and tested, is to merge your branch with the master.

Assignment 2: OOP and Bottles (12 min)

  • Watch this video. Then choose your own real-world class and objects of that class. In the space below, define and name the attributes and methods for your class and the associated objects.

Class: Book Objects: Textbook, novel, manual, and cookbook are all instances of a book. Attributes: Each book has a cover, title, author, and page count. Methods: Each book can be read, held, purchased, or shelved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment