Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save EllieJellyBean/e4e2518a46274c8ae5f9f24c592141e0 to your computer and use it in GitHub Desktop.

Select an option

Save EllieJellyBean/e4e2518a46274c8ae5f9f24c592141e0 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):

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:
  • What are three Slack shortcuts and/or features that stood out? How will each contribute to your productivity?

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:

Questions/Comments/Confusions

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

@EllieJellyBean
Copy link
Author

Learning Fluency
I really connected with this article. I have a bachelor's in Psychology and a Master's in Social Sciences, but I taught an academic writing class at CU Denver. I also worked in the wine industry for most of my adult life. So, I've dipped my toes in quite a few fields but none have ever felt right or connected. This article helped me see that all of those experiences can help me in a way I didn't originally think of.

I also feel like this was helpful to understand the different ways I learn. I was always a good student in school, but I've tried to teach myself different languages and teach myself to code and it didn't go very well. The section about "fluency before understanding" and "discipline before imagination" was what stood out to me the most and made me realize the mistakes I've made in the past when trying to learn something new. I'm planning on putting this quote about my desk because it resonated with me the most: "Understanding does not always lead to fluency, and simply having an eager imagination does not always pass as a shortcut for putting in the hard work."

The first time I really felt like I was "bad at school" was last semester when I tried to take a graduate level Algorithms course (with very little background in discrete math and data structures). I wish I had read this article before I started that class because I think I would've approached my lack of understanding differently. Chunking, repetition, and practice were vital for Simon to learn Mandarin and later computer programming. I plan to keep this in mind throughout my experience at Turing and when things get challenging, I'll look back on all of these suggestions.

Slack Shortcuts

  1. Resource: https://slack.com/help/articles/201374536-Slack-keyboard-shortcuts
    From using Slack in Mod 0, I think I will use the following Slack Shortcuts:
  2. Open the Threads View: Command, Shift, T
  • This I think will be helpful so I stop accidentally starting a new thread instead of responding to one.
  1. Toggle Fullscreen View: ^, Command, F
  • Being able to do this will help with multitasking or asking for help when I'm working on projects that require multiple windows.
  1. Search Current Conversation: Command, F
  • While this is how you search sites normally, it's nice to know that this trick works for Slack too!

What's the Use of the Staging Area in Git?

  1. My old boss needed help organizing her new filing cabinet. She had to throw out her old one, so she took out all of the files and paperwork and put them in relatively organized piles on the floor of her office (it was a massive filing cabinet so it took up most of the floor). I needed to look through the paperwork, make copies of certain documents, then separate and shred any other documents older than 2007 and/or if there was credit card information on it. The rest needed to be refiled in the new filing cabinet. I'm imagining the staging area as the floor with the piles of files with paperwork that I still need to go through. Then, commit would be the new filing cabinet. Originally I imagined this process as a movement of files, but I read another response that the files are being copied. So maybe instead I should imagine it as an original filing cabinet and copies of the paperwork are in the piles, then I need to go through (organize and decide whether to keep or shred) the copies and add those to the new filing cabinet (commit)? Hopefully I'm understanding this right, I am a tiny bit confused about it. I did find this video that someone linked in one of the responses that was helpful: https://www.youtube.com/watch?v=UYtUFKn1hXw&feature=youtu.be

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