Skip to content

Instantly share code, notes, and snippets.

@brycemara
Forked from damwhit/mod_0_session_2_readings.md
Last active July 19, 2020 20:32
Show Gist options
  • Save brycemara/f2e14f98241ab87323204f7bee7941ca to your computer and use it in GitHub Desktop.
Save brycemara/f2e14f98241ab87323204f7bee7941ca to your computer and use it in GitHub Desktop.
Mod 0 Session 2 Readings

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):
  • Improvisation; I hate imrpov, but I can see where it is necessary in code. I hope to learn to use improv in a way that benefits me and my code but also how I learn it and understand it.
  • Strategy; This is right up my alley. Being an engineer and working on projects I always come in with a strategy. I hope to be able to come up with strategies that help me write my code.
  • Something that resonated with me was her description of just jumping into a problem and not knowing what anything meant, she said it was a city with no sidewalks and that none of the signs made sense to her. I would hate to be in that position but I do think I learn best by doing. I think a good way for me to approach projects here at turing i sstudying the basics (as we've been doing) and learning those like the back o fmy hand so when I am in the project I can reference what I do know and peice them together to learn how to create something much bigger and more complicated.

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://slack.com/help/articles/201374536-Slack-keyboard-shortcuts
  • What are three Slack shortcuts and/or features that stood out? How will each contribute to your productivity?
  1. option + shift + up arrow/down arrow. This feature would help move through channels in slack without having to click on each to move. This will contribute to productivity with efficiency (as will most these shortcuts).
  2. command + shift + m. One thing I ddin't really like about slack was having to scroll through all the messages and read them to see if any directly pertain to me. Using this I can see where I was mentioned and what I need to do. This will help me stay on top of my responsibilitites in slack.
  3. command + f. My favorite short-cut, helps me emmesnsly search through long messages/ lots of info for what I need. I use this a lot in research and I'm thrilled I can use it in slack too. Saves me lots of time.

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 worked at bell Helicopter one summer as an intern. The assembly line was a constant subject of my work and I worked on it nearly everyday. I think of staging as somewhat like that assembly line. There's multiple working parts, all on different schedules but all apart of the end game; the helicopter. You can see all different parts working and progress being made in all, here is where you can make the small changes, you can resovle the small conflicts before they come big and you can see how the small changes with benefit the end game.

Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would like 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