Skip to content

Instantly share code, notes, and snippets.

@brycemara
Forked from damwhit/mod_0_session_1_readings.md
Last active July 16, 2020 18:59
Show Gist options
  • Save brycemara/f0b1285cda3da39cf80e648df6d97582 to your computer and use it in GitHub Desktop.
Save brycemara/f0b1285cda3da39cf80e648df6d97582 to your computer and use it in GitHub Desktop.
Mod 0 Session 1 Readings

Session 1 Readings and Responses

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

  • Your key take-aways OR how you're going to implement specific points (minimum 2):
  • A key take away I get is that coding is very much up to the programer. Yes turning will put me in the right place and help me learn and collaborate with multiple coders but at the end of the day I will have to put in the extra effort (aka googling) to be able to truly excel in it.
  • I think that over my time at turing I will get better at being efficient with my googling. Just doing the google work in session 1 practice tasks took me some time, but I'm confident and excited to be able to find websites that make sense to me and places/people I can go to first when running into a problem.
  • 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: When using quotes in the google search engine it will look for the phrase versus just words within the quote. For example, in college I'd use chegg a lot for homework help and I would always find that most my searches only found one or two words that matched and never the entire phrase.
  • Tip 3: When searching for something if you don't want your word to be searched with another hyphen the word not wanted and google will leave it out of the search. When I was searching for array slicing I kept coming up with string slicing and I could have searched 'array slicing -string' and found my answer sooner.
  • Tip 4: If you want to search something on a specific site add site:xyz to the end of the phrase/word you are searching and google will only search it on that site. This will be helpful when searching for something I don't understand in code, an example would be 'variable site:ruby-doc'.
  • Tip 9: Using more phrases is better. When searching for something use one phrase and then use another phrase meaning the same thing separated by an OR and put your phrases in quotes. For example I would search "how to jump a car" OR "jumping batteries in cars".
  • Tip 13: Use words websites would use, most websites won't say "How to wash a shirt" it'd be "Washing Instructions" or something along those lines. When I search code I should try to think more like the computer, "What is a variable?" vs "Variable definition ruby".
  • Tip 14: Short hand, use only important words when using google. "What hospitals were most babies born in in Albuquerque NM around 22 years ago?" versus "1998 birtch rates in ABQ hospitals".
  • Tip 17: If at first you search something and it doesn't come up use different words that are perhaps more common in the speciality you're looking for. "How to make cake" versus "Baking cake instructions".

3. Questions/Comments/Confusions

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

  1. The tips above blew my mind, I didn't know how much easier life could be when searching google.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment