Skip to content

Instantly share code, notes, and snippets.

@damwhit
Last active January 1, 2024 08:55
Show Gist options
  • Save damwhit/33a6cc875b119d49803c801892090141 to your computer and use it in GitHub Desktop.
Save damwhit/33a6cc875b119d49803c801892090141 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):
  • here is what I thought...
  • 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:
  • Tip 3:
  • Tip 4:
  • Tip 9:
  • Tip 13:
  • Tip 14:
  • Tip 17:

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:

@wmcguire18
Copy link

Article 1:

My key takeaway is the cooperative spirit in which we're all working. It struck me that when the author says that we are logically not the first coder to encounter any difficulty, that what we're really doing when we turn to Google is not just the "filling in" of the subtle details of a complex language but calling upon the collective experience of every programmer who has ever worked on this language and chose to record their findings.

@wmcguire18
Copy link

Article 2:

Tips 2, 3, and 4 are all about limiting the search to the most relevant information as quickly as possible: quotes for full strings, hyphens to remove common words that occur with irrelevant uses of the term, and colons to limit the whole search to a single site.

Tip 9 is about getting better results by searching for two concepts in conjunction

Tip 13, 14, and 17 are about our mindset in searching: using the proper words that will produce optimum results, and being flexible enough to try different combinations when our initial approach isn't fruitful.

@Andrey-1992
Copy link

Article 1
Google has become very popular with the past of the years and is available for everyone, but the way this tool can be used it depends in every person. All this information that we have access, can help us or can give us problems. The take-away for this article, it is related to our professional judgment on how we are going to use these tools to complement or reinforce our work based on the data and information that Google gives us. Also, this tool can become a very good reference point to improve our work.

Article 2
Tips 2, 3 and 4:
They are a great tips to improve our search in google, because these three tips have a common thing and it is the use of punctuation attributes in our search, this can help our browser to be more specific and clear in the search. The implementation of "quotes", -hyphen and colon: make a big difference .
Tip 9:
The implementation of multiple words and second words or phrase, helps the browser to have more options and direction to our search on the web. I think the use of synonyms can be a good option for this tip. ("fix my display" & "repair my display").
Tip 13, 14:
These Tips help me to understand that computers language is different than human language and a good way practice their language is trying to think like them. Prioritizing words and organizing my phrases are a good techniques for it. For instances: "What places can I visit in Japan" - "Japan Highlights".
Tip 17:
The perspective is very important for the use of descriptive words in google, because when we are having problems to find something probably we have to try to look in different perspective our point.

@Mstandley1985
Copy link

Article 1:
Google is a fantastic tool. Using it doesn't make you less qualified as a developer...quite the contrary. I liked the Einstein quote as well, "never memorize something you can look up". Also, that when you encounter a problem with code, chances are you're not the first one that's had the problem. Google is a giant database for you to use and will be your best friend in this industry.

Article 2:
2, 3, and 4 were similar in the sense that you're using punctuation to narrow your search query in a very specific way. Using quotes for a specific phrase, hyphen to exclude specific content, or colon to search a specific website.

9: The ability to broaden your search with multiple words.

13: Using professional language helps the search a lot. This also tied into tip 14/17...be specific. No need to clutter the search. Use important or descriptive words only.

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