Mod 0 Session 4 Readings and Responses

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.
• There appear to be a number of suggested workflows out there, seemingly, Gitflow and feature branches are the most popular and are very similar to each other. There is a central repository called the master, and each new scope of work, aka feature, is commited in a branch. You don't want to make the scope of the branches too large so that you can make frequent commits, allowing the new work to be continuously integrated into the project. When beginning work on a new branch, the dev will pull the up-to-date master code and create a new branch with a new that describes the feature being added or changes being done. There may be personal branches and team-wide branches, depending on whether and individual is working on a particular feature or the whole team. Just because a branch is made by someone on the team doesn't mean it will be added to the master code just yet. A pull request is made to notify the team that there is new code up for review and where changes have been made. Generally there is some sort of peer-review as a second set of eyes may allow a different perspective that may be able to catch mistakes or suggest improvements before the code is eventually added to the master. This also allows everyone on the team to be active in each update. This is a simplified look at how developers are able to make colloborative changes using Git to incrementally update their software and work together to make sure that the updates being put out are as free of bugs as is possible.

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 = pen Instances = fountain_pen, ballpoint_pen, gel_pen Attributes = ink_color(string), has_cap?(boolean), length(integer) Methods = write, refill

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/VPAbraham/b36eb2aefca945ca2b857f8b26174f89