Skip to content

Instantly share code, notes, and snippets.

@peeratmac

peeratmac/mod_0_session_2_readings.md

Forked from rwarbelow/mod_0_session_2_readings.md
Last active May 9, 2019 01:37
Show Gist options
  • Save peeratmac/f328ba2496b66505a8fcf669bfa488d7 to your computer and use it in GitHub Desktop.
Save peeratmac/f328ba2496b66505a8fcf669bfa488d7 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):
  • There are more ways than one to study, to learn, to be fluent, or to unserstand something. And you just have to find what is right for you, for example in programming languages, maybe it's not the best to jump right into project for you.
  • I am going to implement the use of exploring ways to learn starting with continuously practicing until that has developed into practiced kill.
  • Fluency works with time and that fluency along with intention, it can work even master. Every day we should see progress with hard studying and keep on at it.
  • I really like the author's sketchbook front pages, it said, fluency before unstanding and discipline before imagination.

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

https://codinginflow.com/google-programming-questions << use this instead, the website above is down as of 05/06/19 MON.

  • Your key take-aways OR how you're going to implement specific points (minimum 3):
  • Do a lot of searches, don't just stick to one source, first step is usually to get an overview from official documentation and then onto other blog posts.
  • Make sure as you read and go through the different sources, spot any common trend and mistakes, spot questions that come up often.
  • Use Tools in menu under searchbox on Google to narrow time span if you suspect what you are searching is prone to change, can adjust later to increase more months or years if the results are not enough.
  • Images search can also be helpful as sometimes there are different implementations and results for the same topic, having an image to see can help you narrow to what you are really looking for.

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):
  • Google as much as I need to.
  • Google is an essential part of our software development toolkit and we should know when and how to use it.
  • No need to remember everything especially for minor details and especially when you program in multiple languages.

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: If there is something specific, use quotes for Google search. The whole phrase will be used instead of maybe 3 words in the phrase in any order. Example: "Becoming interview" by Michelle Obama
  • Tip 3: Hyphen can be used to exclude words you don't want to see in the results. Example: tiger -cheetah
  • Tip 4: Colon can be used to specific what sites you want to see content on. Example: learn programming in colorado site:www.turing.io
  • Tip 9: Multiple words or phrases being searched at the same time to get a more accurate response. Example: "CSS gradient OR How to use CSS gradient"
  • Tip 13: Use words that websites would use and not words that people normally say in everyday life. Example: "What do i have when i feel sore throat" could be replaced by "sore throat symptoms"
  • Tip 14: Only use important words because when including too many words, it may limit your results and also slower to find what you are looking for. Example: don't use "how to console log printing output in javascript" instead try: "console log in javascript"
  • Tip 17: Descriptive words should be used, specific words that go along with your definition or just say it in a different way that may be more common to help with your results. Example: "pancake ingredients waffle" but what you really mean is "how to cook waffle with pancake ingredients"

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
@katiescruggs
Copy link

Good job, @peeratmac!

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