Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save slkarsh/15cd2bf96c19ecc5da8abab7b6d7960a to your computer and use it in GitHub Desktop.
Save slkarsh/15cd2bf96c19ecc5da8abab7b6d7960a 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/217626598-Get-around-faster-with-keyboard-shortcuts

  1. https://slackhq.com/slick-features-and-capabilities-you-didnt-know-about-in-slack
  • What are three Slack shortcuts and/or features that will contribute to your productivity?
  1. Command + k to easily search files and channels especially
  2. command + shift + k to easily search between DMs (I imagine this will be super handy later as I utilize Slack more and more)
  3. Knowing how to mark a message as unread. This is something I do in my current job all the time with emails so I remember to follow up on them, so I'm glad there's a way for me to do that in Slack as well!

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: I envision the git staging area like people lining up to go down a water slide, and the lifeguard only lets one or two people go down at a time. Everyone in line is in the staging area, and the "commit" is the person/pair going down the water slide. With git you don't want to commit too much all at once and have a cascade of unintended effects you have to sort through to try and find the source of the problem. Same thing with a bunch of people going down a waterslide - there will probably be some giant cluster and stall, but pinpointing the individual source would be a headache, to say the least.

Questions/Comments/Confusions

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

@katiescruggs
Copy link

Great job, @slkarsh!

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