Read on Twitter
20/21 hindsight: comps are an outdated hazing ritual, but it's a good practice-run for trying to synthesize your unique argument out of a whole buncha discourse. It's hard. And I can't help with the content.
But I can help with organizational tips:
a
... https://twitter.com/MeredithBessey/status/1381585790061449218
But I can help with organizational tips:
a
... https://twitter.com/MeredithBessey/status/1381585790061449218
Echoing others, yes to Zotero: you can make notes and each has a URL. (I've found these to be helpful when I've wanted to share these note-files with collaborators or even build a public-facing bibliography.)
I've use Evernote for this too (which can also internally hyperlink).
I've use Evernote for this too (which can also internally hyperlink).
To help you in the long-term, aim for an expanded annotated bibliography:
1. paraphrase their argument
2. summarize their lineage (building on who? previous args?)
3. explain key interventions, define terms
4. note limitations
5. write your takeaways/reactions
1. paraphrase their argument
2. summarize their lineage (building on who? previous args?)
3. explain key interventions, define terms
4. note limitations
5. write your takeaways/reactions
If relevant, select *a* quotation but be very choosy.
As in, pick one.
This way, you can reference these readings later and get a gist of the text without having to reread the whole thing. It's meant to give you just enough context you can use your notes in the exam and beyond.
As in, pick one.
This way, you can reference these readings later and get a gist of the text without having to reread the whole thing. It's meant to give you just enough context you can use your notes in the exam and beyond.
If you already know some of the keywords or the concepts you'll be working with, build in a tagging system.
This can be as fancy as hashtags, but it can also be as quotidian as a bolded list at the end of your notes so that you can use command-f. This way, you'll code as you go.
This can be as fancy as hashtags, but it can also be as quotidian as a bolded list at the end of your notes so that you can use command-f. This way, you'll code as you go.
Name all your digital texts in the same way for easy managing. I usually do author last name, year, title. If a keyword is buried somewhere in-text, I'll add it in parenthesis for easy searching later on.
e.g. Barad_2007_meeting the universe halfway (intra-action).pdf
e.g. Barad_2007_meeting the universe halfway (intra-action).pdf
And of course, the pincher: when I read non-digital texts, I rely heavily on color-coded post-it notes: one color for the author's theoretical concepts, one for their methodological approach, one for my "notes to self", one for my argument. I use the same colors in digital notes.
This is definitely not the only way to make sense of academic chatter, but I'm hoping some of these tips will help #gradstudents as comps season approaches. And as you figure out a system that works *for you*, do that.
#thatdoctorallyfe #AcademicChatter #YouGotThis
#thatdoctorallyfe #AcademicChatter #YouGotThis
