Mod 0 Session 2 Readings

mod_0_session_2_readings.md

Session 2 Readings and Responses

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

Learning Fluency by Turing alum Sara Simon (35 min)

• Your key take-aways OR how you're going to implement specific points (minimum 3):
• Thinking ahead -- I definitely do not do this enough. Pseudocoding and planning are weak points for me.
• Daily practice -- I need to develop a method of daily practice so I can work on algorithms daily; I don't want to memorize them, per se, just know them well enough that I can do them spontaneously. (I'll need a bank of algorithms, too)
• Developing my small group team -- having a great team helps develop skills, and I want to facilitate that for my team.

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. Personal experience and slack.com

• What are three Slack shortcuts and/or features that stood out? How will each contribute to your productivity?

1. Using : and a keyword is a quick way to insert emojis. 😄
2. command + n for a new message
3. the call actions -- I never knew! I'll use those when I'm on a call in the future.

What's the use of the staging area in git? on Stackoverflow (15 min)

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'm not sure it's a metaphor, but my best explanation of it is command-z (undo). If command-z only worked for multiple changes, it would not be nearly as useful. The reason it is so useful is because it goes back one step at a time. That's what using frequent commits does, is it breaks down lots of changes into smaller chunks so we can find errors easier (if necessary), review those changes easier, and clean up easier.

Questions/Comments/Confusions

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

1. No questions, but I really appreciated the refresher on more obscure git commands. It's incredibly useful and powerful and I think we can take it for granted when we're not using all of the functions that it has.

🙌