Using the internet ot search for answers to problems is a tool essential to everyone's success. This discussion covers Google and Stackoverflow.
While you may be familiar with Google and Stackoverflow the material here may supplement your knowledgeor surprise you.
How do you use Google? Do you rely on the top search results?
https://www.wired.com/2011/11/st_thompson_searchresults
While google is really good, and provides the best available search results you should always be assessing the results.
When you search these are questions you should be asking:
- How accurately do these results match the answer I'm looking for?
- How credible/knowledgeable is the source?
- When was this answer published?
When the results are not as accurate as you would like look closely at the search terms you have used and think of how you can refine them for better results.
These tactics can help
- Remove unneccessary words
- Refining terms
- Rephrasing the question
Keep searching, while Google is very good at what it does sometimes the first set of results will not be what you are looking for.
Use effective keywords. The more descriptive you can be the better your results.
Google matches key words:
- A who
- The Who
- Who
Order matters:
- Sky Blue
- Blue Sky
Search term modifiers:
When confronted with an error message you'll need to identify the section that best describes the error. Usually the best information will at the top of an error.
Many times part of the error will contain identifiers that you have created these may not be relevant.
Playground execution failed: error: Equatable.playground:5:25: error: 'Self' is only
available in a protocol or as the result of a method in a class; did you mean 'Person'?
static func ==(lhs: Self, rhs: Self) -> Bool {
^~~~
Person
error: Equatable.playground:5:36: error: 'Self' is only available in a protocol or
as the result of a method in a class; did you mean 'Person'?
static func ==(lhs: Self, rhs: Self) -> Bool {
^~~~
Person
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x000000010c83d360 com.apple.dt.Xcode.PlaygroundStub-macosx`executePlayground
frame #1: 0x000000010c83b22a com.apple.dt.Xcode.PlaygroundStub-macosx`-[PlaygroundViewBridgeService execute] + 90
frame #2: 0x00007fff80187b8c CoreFoundation`__invoking___ + 140
frame #3: 0x00007fff80187a11 CoreFoundation`-[NSInvocation invoke] + 289
frame #4: 0x00007fff801a1196 CoreFoundation`-[NSInvocation invokeWithTarget:] + 54
frame #5: 0x00007fff93a923d6 ViewBridge`__68-[NSVB_ViewServiceImplicitAnimationDecodingProxy forwardInvocation:]_block_invoke + 47
frame #6: 0x00007fff93ab0fe9 ViewBridge`__runAnimationGroup_block_invoke + 21
frame #7: 0x00007fff7e5d1846 AppKit`+[NSAnimationContext runAnimationGroup:] + 58
frame #8: 0x00007fff7dc99bea AppKit`+[NSAnimationContext runAnimationGroup:completionHandler:] + 85
frame #9: 0x00007fff93ab0fc5 ViewBridge`runAnimationGroup + 303
frame #10: 0x00007fff93a91edd ViewBridge`+[NSVB_View _animateWithAttributes:animations:completion:] + 507
frame #11: 0x00007fff93a92358 ViewBridge`-[NSVB_ViewServiceImplicitAnimationDecodingProxy forwardInvocation:] + 156
frame #12: 0x00007fff8018654a CoreFoundation`___forwarding___ + 538
frame #13: 0x00007fff801862a8 CoreFoundation`__forwarding_prep_0___ + 120
frame #14: 0x00007fff80187b8c CoreFoundation`__invoking___ + 140
frame #15: 0x00007fff80187a11 CoreFoundation`-[NSInvocation invoke] + 289
frame #16: 0x00007fff801a1196 CoreFoundation`-[NSInvocation invokeWithTarget:] + 54
frame #17: 0x00007fff93a608a2 ViewBridge`-[NSVB_QueueingProxy forwardInvocation:] + 327
frame #18: 0x00007fff8018654a CoreFoundation`___forwarding___ + 538
frame #19: 0x00007fff801862a8 CoreFoundation`__forwarding_prep_0___ + 120
frame #20: 0x00007fff80187b8c CoreFoundation`__invoking___ + 140
frame #21: 0x00007fff80187a11 CoreFoundation`-[NSInvocation invoke] + 289
frame #22: 0x00007fff801a1196 CoreFoundation`-[NSInvocation invokeWithTarget:] + 54
frame #23: 0x00007fff8018654a CoreFoundation`___forwarding___ + 538
frame #24: 0x00007fff801862a8 CoreFoundation`__forwarding_prep_0___ + 120
frame #25: 0x00007fff80187b8c CoreFoundation`__invoking___ + 140
frame #26: 0x00007fff80187a11 CoreFoundation`-[NSInvocation invoke] + 289
frame #27: 0x00007fff801a1196 CoreFoundation`-[NSInvocation invokeWithTarget:] + 54
frame #28: 0x00007fff8018654a CoreFoundation`___forwarding___ + 538
frame #29: 0x00007fff801862a8 CoreFoundation`__forwarding_prep_0___ + 120
frame #30: 0x00007fff80187b8c CoreFoundation`__invoking___ + 140
frame #31: 0x00007fff80187a11 CoreFoundation`-[NSInvocation invoke] + 289
frame #32: 0x00007fff93ab5579 ViewBridge`withHintInProgress + 487
frame #33: 0x00007fff93ab52b0 ViewBridge`__deferNSXPCInvocationOntoMainThread_block_invoke_2 + 233
frame #34: 0x00007fff93a39459 ViewBridge`+[NSViewServiceApplication withHostPID:invoke:] + 46
frame #35: 0x00007fff93ab5173 ViewBridge`__deferNSXPCInvocationOntoMainThread_block_invoke + 179
frame #36: 0x00007fff93ab4d67 ViewBridge`__deferBlockOntoMainThread_block_invoke_2 + 544
frame #37: 0x00007fff801aa17c CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
frame #38: 0x00007fff8018af84 CoreFoundation`__CFRunLoopDoBlocks + 356
frame #39: 0x00007fff8018aac6 CoreFoundation`__CFRunLoopRun + 1878
frame #40: 0x00007fff8018a114 CoreFoundation`CFRunLoopRunSpecific + 420
frame #41: 0x00007fff7f6eaebc HIToolbox`RunCurrentEventLoopInMode + 240
frame #42: 0x00007fff7f6eacf1 HIToolbox`ReceiveNextEventCommon + 432
frame #43: 0x00007fff7f6eab26 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 71
frame #44: 0x00007fff7dc83a54 AppKit`_DPSNextEvent + 1120
frame #45: 0x00007fff7e3ff7ee AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
frame #46: 0x00007fff93a3a628 ViewBridge`-[NSViewServiceApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 100
frame #47: 0x00007fff7dc783db AppKit`-[NSApplication run] + 926
frame #48: 0x00007fff7dc42e0e AppKit`NSApplicationMain + 1237
frame #49: 0x00007fff95b638c7 libxpc.dylib`_xpc_objc_main + 775
frame #50: 0x00007fff95b622e4 libxpc.dylib`xpc_main + 494
frame #51: 0x00007fff93a64c85 ViewBridge`-[NSXPCSharedListener resume] + 16
frame #52: 0x00007fff93a3f316 ViewBridge`NSViewServiceApplicationMain + 2985
frame #53: 0x000000010c83d3a2 com.apple.dt.Xcode.PlaygroundStub-macosx`main + 34
frame #54: 0x00007fff9590a235 libdyld.dylib`start + 1
Try these searches. Imagine you want to randomize an array of objects and you need the process to be as random as possible.
Split into teams, each team searches for one of the ideas below.
- Learn how to rearrange the elements of an collection?
- Understand how random are random numbers?
- Get maximum randomness out of random numbers?
- Find a service that delivers very random numbers?
- http://www.lifehack.org/articles/technology/20-tips-use-google-search-efficiently.html
- http://www.byrdseed.com/teaching-search-skills/
Google has a bunch of built in utilities. Some of these are fun diversions while others are truly useful tools.
- Definition
- Calculator
- Timer
- Conversions
- Translations
- Images
- Games
- Easter eggs
- Do a barrel roll
- Zerg Rush
Google has done a great job making the Google search engine an amazingly easy tool to use. Look at it closely. There tool is not an accident, it has evolved and improved over time.
Anyone who has a question about software development has seen answers to common questions on Stackoverflow. This discussion will take a closer look at Stackoverflow.
Here is how Stackoverflow describes themselves:
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed answers to every question about programming.
Stack Overflow is a great place to find answers.
There are Stack Exchanges for almost every topic.
Look at the stack exachanges for things that you enjoy that aren't necessarily software related.
Reputation
Stackoverflow is a good place to build a reputation. This is good for job applications.
Things to avoid
People can be snarky. Ignore rude behavior if you encounter it. do not take any conversation on the internet personally.
Remember! While diamonds last a life time the internet is forever!
What to look for when reading a question
Look for questions that outline and describe a specific question or problem.
Look for things the post may have already tried.
Look for code samples.
What to look for in an answer
Besides the answer read the comments.
Look for code samples.
When asking questions:
- Write a clear description. Short and to the point. avoid unnecessary language. Strive for terse but accurate.
- Include solutions that you have tried already.
- Include only the relevent portion of any error messages.
- Format the errors.
- Include a code snippet. Use Stack Overflow's formmatting.
- Proof read your work before submitting.
When answering questions:
- Write a clear and intelligable answer.
- Avoid trying to sound smug or snarky.
- Avoid extraneous language.
- Use formmatting. Especially for code samples.
- Answer your own questions when you can.
The most imporant thing to remember when using Stackoverflow is to be profesional.
Stack Overflow provides a great look into the world of developers. This is a survey of developers on Stackoverflow that covers a wide range of metrics. The information is informative and interesting.
What are some outstanding facts?
Stackoverflow provides a service called Developer Story. This acts as an online resume for developers. Consider joining and using it to track your progress and work.
- Make an account on Stack Overflow.
- Search for a solution to the random array?
- Add a comment.
- Up vote the answer you agree is best.
- Ask a question.
- Think of a question you had this week.
- Post the question.
- Notice the question may already exist! The site suggests existing questions.
- Explain your question as clearly and concisely as you can.
- Format your answer!
- Use tags.
- Follow the rules for tags.
- Look at new questions and try your best to provide an answer.
-
Format your answer.
-
Write a good answer. Keep it clear and concise.
-
Who can get the highest rep?
-
Did anyone earn a badge?
This is a feature that acts like your resume on Stack Overflow. You can build it over time.
Start your developer story.