Skip to content

Instantly share code, notes, and snippets.

@vrandall66

vrandall66/mod_0_session_4_readings.md

Forked from rwarbelow/mod_0_session_4_readings.md
Last active May 15, 2019 22:58
Show Gist options
  • Save vrandall66/579d3b7fe48f0ff92e2d9f5e3dbc923f to your computer and use it in GitHub Desktop.
Save vrandall66/579d3b7fe48f0ff92e2d9f5e3dbc923f 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.

Git and GitHub allow developers to work on collaborative projects from multiple remote locations by pulling the entire repository (or certain parts of it) onto a local computer so that edits can be made on a non-live version, and any updates or changes to the pre-existing code can be pushed to the Hub for all collaborators to see, while holding onto the older versions of the program. As soon as changes have been pushed by one or more developers, the other developers can pull the updated repository onto their local computer so they are working with the version of the code that everyone else is working with. If suddenly after pushing and pulling the new code issues arise, the previous versions of the repository still exist and can be made live until the bugs are fixed.

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

    1. Class: Lightbulb. Objects: LED Floodlight, Outdoor Floodlight, Indoor Floodlight, Turn signal bulb, headlight bulb, brights (auto), traffic light bulb, spotlight bulb, etc. Attributes Wattage, Lumens, Color Temperature, Dimensions, etc. Methods Estimated remaining lifespan
    2. Class: Sneaker Objects: SKU/UPC#, SKU/UPC#, SKU/UPC#, SKU/UPC#, SKU/UPC#... Attributes: Brand, Style, Heel height, Sole Material, Material, etc. Methods: Is this a good running shoe? Is this shoe included in the Memorial Day Sale? etc.
    3. Class: Car Objects: Ford Escape, Chevy Silverado, Volkswagen Bug, Dodge Ram, etc. Attributes: Brand, Engine, Type, Wheel Drive, Average Mileage, VIN, etc Methods: How much gas is in tank?

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, 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/vrandall66/125186006bd674182ebf39ec09b04b61

@katiescruggs
Copy link

Good job, @vrandall66! Your object examples are nice.

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