Skip to content

Instantly share code, notes, and snippets.

@tylorschafer

tylorschafer/mod_0_session_2_readings.md

Forked from rwarbelow/mod_0_session_2_readings.md
Last active May 9, 2019 01:39
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save tylorschafer/3277c10d9026375d9891e59badfdc6b1 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save tylorschafer/3277c10d9026375d9891e59badfdc6b1 to your computer and use it in GitHub Desktop.
Download ZIP
Mod 0 Session 2 Readings
Raw
mod_0_session_2_readings.md

Session 2 Readings and Responses

The readings and responses listed here should take you approximately 60 minutes.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of this document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

1. Learning Fluency by Turing alum Sara Simon (30 min)

  • Your key take-aways OR how you're going to implement specific points (minimum 3):
  • I really loved how Sara begins by telling her background and alluding to how "different" she is from the old status quo of developers. I like Sara, have not been destined to be a developer from the get-go, but have a history of learning other language. I was involved with music for a long time growing up which I have always believed to be a language in itself. I learned how to improvise, practice (in a 'chunking' like manner i.e ENDLESS SCALES!!), memorize small bits of information to bring into a larger whole of understanding how to be 'fluent' in music.
  • Sara talks about how fluency requires familarity from 'repeated and varied interaction'. Again this is a very familiar concept to me growing up as a musician, and I plan on using the same process in learning how to code. I'm very aware of how learning this new type of language will take alot of repetition and varied practice in order to develop fluency and discpline.
  • I also really liked Sara's telling of her Middlebury language program and how intense that summer was for her, but how valuable that learning was in the end. Clearly Turing shares many similarites with that program, we will be immeresed in a language every day that we will slowly build and develop on. I particularly think that I will devlop with my classmates the same bond Sara had with her Mandarin group, in that we will all have limited programming vocabularies at first. This will help in learning concepts together, working through problems with the help of varying prespectives.
  • Overall I just loved how Sara emphisizes the importance of learning to be fluent in a language befoe trying to be 'innovative' or 'creative'. She makes it clear that you cannot properly be an innovator until you put in the work of intimately knowing as much as you can about what you are trying to innovate.

2. How to Google Programming Problems Effectively by Lulu Li (15 min)

  • Your key take-aways OR how you're going to implement specific points (minimum 3):

  • We replaced this article with the "How to Use Google to Solve your Programming Questions". This reading had some overlap with the "20 Google Search Tips" article. However I found the first point of this article to contain alot of useful information. I will definitley be utilizing his strategy of starting with a broader search on the language, then looking into offical documentations, and then following with tutorials after that.

  • I particularly like the idea of searching many different posts and not sticking to one source, as it gives you alot of different perspective and different approaches to your question.

  • I will definitley be implementing narrow time span searchs in google, to make sure I get the most current/relevant answers to my questions.

3. Do Experienced Programmers Use Google Frequently? by Umer Mansoor (10 min)

  • Your key take-aways OR how you're going to implement specific points (minimum 2):
  • This article reaffirmed my belief that google is just a wonderful tool for troubleshooting problems. I have used DAWs (Digital Audio Workstations) for years to make music and google was my only resource to 'validate my logic' as the author states. I'm happy to hear that there isn't a stigma on using google for coding because I know I will be using it constantly.
  • I like the idea of using google to research possible solutions and not copy-pasting answers, rather use it to learn about your problem and work out your own solution with the help of others.
  • I never heard that Einstein quote before, "never memorize something that you can look up." It's funny how relevant that is today with a tool like google. Makes me wonder what Einstein could have accomplished in todays world!

4. 20 Google Search Tips to Use Google More Efficiently by Joseph Hindy (15 min)

  • Briefly describe (in your own words) each of the tips below AND provide an example of a search that captures the sentiment of the tip
  • Tip 2: Use quotes to search a phrase exactly as you typed it. I have to note that I NEVER KNEW THIS! This is going to be extremely helpful in the future. For example if I wanted to find a niche phrase or item, lets say "sweater made of human hair", then I wouldn't get articles about "how to remove human hair from your sweater". (I have a wierd sense of humour...)
  • Tip 3: Using a hyphen will exclude words you don't want to include in your search. This is another super helpful tip. If I wanted to search for information on the Game of Thrones book and not the TV show, I could search: Game of Thrones characters -tv show.
  • Tip 4: If you want to search for results on a specific site use a colon followed by the website. Avengers Endgame site:ign.com
  • Tip 9: Use OR to search multiple words or phrases at the same time. Broncos new tight end OR Broncos first round draft pick. This allows you to search multiple wordings and phrasings to help narrow down a search.
  • Tip 13: Google words and phrases that sound like they would appear on a professional website, rather than googling questions in informal language. "why is my computer screen dark" should be phrased "change brightness settings in OSX."
  • Tip 14: Limit your searches to the most important words. Over wording a google search will limit or ruin your search results. Instead of googling: "Why is my netflix audio so distorted on my phone?" I may google instead "netflix mobile app audio distortion."
  • Tip 17: Think about your wording and use descriptive words to be as specific as possible with your searches. I always find that using words like "troubleshoot" are far more specific than using the phrase "how to". "troubleshoot audio driver in Ableton" vs. "how to fix audio driver problem in Ableton."

5. Questions/Comments/Confusions

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

  1. N/A, the readings were all very straight forward and very insightful.
@katiescruggs
Copy link

katiescruggs commented May 9, 2019

Good job, @tylorschafer! Glad the readings were insightful!

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