update to improve the suggestions for code review requests

Author: katyhuff

manual/guides/katy/codereq.md

@@ -5,17 +5,18 @@ subtitle: "You have a bug. I am not your only hope."
 permalink: /manual/guides/katy/codereq
 ---
 
-![Googling the Error Message](https://pbs.twimg.com/media/CfFPuvoWwAALmcC.jpg "The most important fake book of our time."){:width="270px"}
+![Googling the Error Message](https://raw.githubusercontent.com/denitdao/o-rly-collection/refs/heads/main/public/book_covers/google-error-message.jpg "The most important fake book of our time."){:width="270px"}
 ![Trying Stuff Until It Works](https://pbs.twimg.com/media/CfSQdwUW8AErog1.jpg:large "Another important fake book on persistence."){:width="270px"}
 
+
 # Google it
 
 Please don't come to me with a question that can be solved by a Google search 
-of the error. Especially if you are a Millenial from the U.S., Google really 
-should be in your blood by now. For better google skills, consider 
-[powering up your search tactics](http://www.powersearchingwithgoogle.com/course/aps/skills).
+of the error. In these modern times, Google really 
+should be in your blood by now.
 
-Once you google it, of course, try the things you found on google. 
+Once you google it, of course, try the things you found on google, take notes, 
+and read the errors for clues. 
 
 # Stack Overflow
 
@@ -58,14 +59,29 @@ you will need to formulate a [Minimal Working
 Example.](http://stackoverflow.com/help/mcve)
 
 Yes, sometimes a minimal working example is hard to create. If that's the case, 
-I understand. However, you should still do what you can to document what you 
-are trying to do, how you got where you are, how you tried to fix it. I will 
-need this information to help you.
+I understand. However, simply the act of creating one is often enough to 
+provide clues about the source of the error. As you proceed, please do what you 
+can to document what you are trying to do, how you got where you are, how you 
+tried to fix it. I will need this information to help you.
+
+# Collaborate
+
+You're probably in the office as you're doing your research, so you have an 
+excellent resource very nearby! Your colleagues! You might just show them the 
+error you're dealing with, or share your minimal working example on GitHub.  
+Either way, try discussing it in person or on Slack with the other students, 
+and maybe they can help.
 
 # Contact me
 
-If you have tried _everything_ above and nothing has been clarified, then 
-should you email me.  The email should include your minimal working example or 
+There should be ample opportunities to ask me quick questions about what you 
+can try to solve your bug -- try to drop by Coffee Chat or pop by my office if 
+you think it'll only take a few minutes. 
+
+If you have tried _everything_ above and nothing has been clarified,  and you 
+think it might take a while to debut, then 
+should you email me or Slack message me.  If possible, it should point to details somewhere (ideally 
+GitHub or a Gist) about your minimal working example or 
 your detailed documentation of the problem (above). I may need a few days to 
 look it over (so you may as well also add it to Stack Overflow in case they're 
 faster than me.) If I can't help you fix it by email, I'll let you know we