Skip to content

Instantly share code, notes, and snippets.

@sertmer

sertmer/mod_0_session_4_readings.md

Forked from rwarbelow/mod_0_session_4_readings.md
Last active June 3, 2019 17:11
Show Gist options
  • Save sertmer/3f16ab7b5584c281b38fa9136e03c8a5 to your computer and use it in GitHub Desktop.
Save sertmer/3f16ab7b5584c281b38fa9136e03c8a5 to your computer and use it in GitHub Desktop.
Download ZIP
Mod 0 Session 4 Readings and Responses
Raw
mod_0_session_4_readings.md

Session 4 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 (30 min)

Read Turing Instructor David Whitaker'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.
  • I find it most usefull to think of git workflow as being similar to google docs, or cloud saving/sharing. I can work on my project at work, pushing my commits to github when I feel ready. When I get home and have the itch to work some more, I can pull those commits down onto my home computer along with the changes my teammates might have pushed, and that way I can be sure I'm working on the most updated version of the project, no matter where I am, or when I want to work. When I'm done, I make some commits with annotation of what was done, and push it back to github, so that the next person to work on it has all of the information they need to pick up where I left off.

Assignment 2 (10 min)

  • Watch Tim's video on classes and objects.

  • In the space below, come up with your own example of a class (like "bottle") and several objects (like "spray bottle", "nalgene", etc.):

  • Class: Marker. Instances: Dry_Erase_Marker, Paint_Marker, Permanent_Marker,

Assignment 3 (60 min)

Skim this intro to Markdown. It's not necessary to memorize because you can always come back to it as a reference.

Next, create a new gist of your own by clicking the New Gist button in the upper right-hand corner of the screen. Create a "Beginners Guide to Git" documenting your git knowledge so far using Markdown. Incorporate each of the following features into your Gist:

  • at least two headings of different sizes

  • at least one numbered list

  • at least one bullet point list

  • at least one bold word/phrase

  • at least one italic word/phrase

  • at least one code block

  • at least one inline code block (greyed text)

  • at least one image

  • Paste the link to your gist here: https://gist.github.com/sertmer/012d7d6b3e27d673b227fcc521d850b8

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