Editing How to learn from a thing that's not your thing

From CommunityData

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
Learning from a thing that's not your thing is a necessary part of scholarship: it can be generative and exciting. It can also be boring and overwhelming. The invitations go out constantly, tugging at your sleeve to bid for your time. Sometimes "nope" is the right answer, but it turns out that saying "yep" is often a good idea.
Graduate school and academic culture is filled with all kinds of events and activities -- some highly related to your research, some not. Attending these events and learning from them is part of the "hidden curriculum" of graduate school -- but that means the lessons to be learned can be a bit implicit. Although it might make a lot of sense to attend these events to learn these lessons, the vague/hidden nature of the lessons can make a person feel lost and maybe be a waste of time too. This page is a list of concrete lessons to be learned from varying kinds of events that happen, and the kinds of lessons that can be learned from going to them even if they're not related to you area of work.


Graduate school and academic culture is filled with all kinds of events and activities—a few are highly related to your research, but most things will not be squarely in your wheelhouse. Attending these events and learning from them is part of the "hidden curriculum" of graduate school—but that means the lessons to be learned can be a bit implicit. Although it might make a lot of sense to attend these events to learn these lessons, the vague/hidden nature of the lessons can make a person feel lost. If one goes in expecting explicit connections to one's own work, letting unrelated work just wash over you may feel like a waste of time. This page is a list of concrete lessons to be learned from varying kinds of events that happen, and the kinds of lessons that can be learned from going to them even if they're not related to your area of work.
===Job Talks===


===Departmental Lectures, Colloquia, Special Speaker Things===
* What goes into a job talk?
* Is it terrifying? What does awkward and unprepared look like?
* How does someone summarize a body of work into an interesting story that can appeal to a broad group but still sound scholarly?
* What kinds of questions do people ask?
* Who will attend my job talk?


* If it's your department and during daylight hours, you probably should go. Because probably someone is noticing who goes.
===Defenses===
* What does the organizer do? When it's your turn to organize a thing like this, what will you need to know?
 
* Unrelated to your thing? Thank goodness. Someone is about to save you a lot of time, because they'll summarize an area of knowledge and work for you, and that means you don't have to read the books and take the classes to at least be conversant enough in the topic to know it's not related to your thing -- or what the connections might be.
* What goes into a defense?
* Imagine the dinner party conversation: if you wanted to explain your work to this speaker, would they care? Why? What connections might you make between your ideas and theirs to charmingly draw them into a conversation that's productive for you both?
* Is it terrifying? What does awkward and unprepared look like?
* Imagine the reviewer response: if the speaker were on a review panel, board, or other entity evaluating your work in a field of diverse work (most of which, like your thing, is not their thing....), why would they pick you and your work to publish, award, hire? What feedback would they have for your research?
* What's the flow of who speaks when and how much?
* What's at stake, why this speaker, how do they structure the argument, how would you do it, where do they fall short?
* How does someone summarize a body of work into an interesting story that can appeal to a broad group but still sound scholarly?
* How specific should I get?
* What kinds of questions do people ask?
* Who will attend my defense? Who do I want to invite?


===Workshop===
===Workshop===
Workshops vary widely. Some are a weekly gathering of folks sharing their work and helping each other (and if you're going to bring work to such a place, you definitely should pay in with your time --- if it's a group of 8, meeting for an hour with an hour of prep to participate, you'll get back 16 hrs of work from others when it's your turn, so plan to pay that same amount into the pool). Some are oriented to a theme, might be conceptual or tutorial in nature, and happen only for a limited time (perhaps with a conference). Some entire conferences call themselves workshops. This is about the first category of workshop (the work-sharing kind).
Workshops vary widely. Some are a weekly gathering of folks sharing their work and helping each (and if you're going to bring work to such a place, you definitely should pay in with your time --- if it's a group of 8, meeting for an hour with an hour of prep to participate, you'll get back 16 hrs of work from others when it's your turn, so plan to pay that same amount into the pool). Some are oriented to a theme, might be conceptual or tutorial in nature, and happen only for a limited time (perhaps with a conference). Some entire conferences call themselves workshops. This is about the first category of workshop.


* What kinds of questions do authors ask? What kinds of answers do they get?  
* What kinds of questions do authors ask? What kinds of answers do they get?  
* What kinds of concerns do people express?
* What kinds of concerns do people express?
* What goes unsaid?
* What goes unsaid?
* With the feedback the person is getting, what kinds of changes would you expect to see them make?
* Can you see what someone means when they bring up an opportunity to improve?  
* Can you see what someone means when they bring up an opportunity to improve? Did they see something you don't? Did they miss something you see clearly?
* What is this work they're citing, is it interesting?
* What is this work they're citing, is it interesting?


Line 35: Line 41:
* Fess up and just listen.  
* Fess up and just listen.  
* Use the comments that people make to build a summary or set of notes for yourself in your zotero. You might find it useful later.
* Use the comments that people make to build a summary or set of notes for yourself in your zotero. You might find it useful later.
===Job Talks===
* What goes into a job talk?
* Is it terrifying? What does awkward and unprepared look like?
* How does someone summarize a body of work into an interesting story that can appeal to a broad group but still sound scholarly?
* What kinds of questions do people ask?
* Who will attend my job talk?
===Defenses===
* What goes into a defense?
* Is it terrifying? What does awkward and unprepared look like?
* What's the flow of who speaks when and how much?
* How does someone summarize a body of work into an interesting story that can appeal to a broad group but still sound scholarly?
* How specific should I get?
* What kinds of questions do people ask?
* Who will attend my defense? Who do I want to invite?
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)
Retrieved from "https://wiki.communitydata.science/How_to_learn_from_a_thing_that%27s_not_your_thing"
Attribution-Share Alike 3.0 Unported
Powered by MediaWiki