Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save JamesRexMiller4/d4919228f6656ce5079aba42a33c61b7 to your computer and use it in GitHub Desktop.
Save JamesRexMiller4/d4919228f6656ce5079aba42a33c61b7 to your computer and use it in GitHub Desktop.
Mod 0 Session 3 Readings

Session 3 Readings and Responses

The readings and responses listed here should take you approximately 20 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.

Slack Shortcuts and Features (10 min)

Use Google to go find at least one online resource detailing keyboard shortcuts and/or features that are built into Slack.

  • What resource(s) did you find? Paste them below:
  1. https://get.slack.help/hc/en-us/articles/201374536-Slack-keyboard-shortcuts
  • What are three Slack shortcuts and/or features that will contribute to your productivity?
  1. Clear all unread messages : Shift + Esc
  2. Mark message as unread : Option + click
  3. Emoji shortcut : Command + Shift + \

The idea of the staging area is frequently one of the trickiest concepts to wrap your head around when you're first learning git. Read the question and answers (or do your own Googling on the git staging area). Then, create your own metaphor comparing the staging area to something in real life.

  • Type your metaphor below:

The Git staging area is an intermediary zone where one can decide to fully enact a change to a file/ git repository. The metaphor I think of is when Regis Philbin asks you to say final answer when you make your selection on Who Wants to be a Millionaire? I also see the value of the staging area as it applies to multiple people making changes to a file at the same time. This results in merge conflicts and forces a user to review and correct before being allowed to commit. This is very important when people are working on overlapping tasks so that one persons code is not overwritten by another commit without a review.

Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would an instructor to address, list them below:

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