PhD Stuff


This is a guest post by my esteemed former colleague, John Goodrich, who started a year behind me and only finished a few months after me. Even at his lazy pace, he was able to get two articles published by the time he graduated: see NTS 56.1 (2010) on Rom 16.23 and JSNT 32.3 (2010) on Gal 4.1-2. Here’s a few ideas he offers. Thanks for this John.

Things I did that I recommend for others…

Before you start:
- Purchase and familiarize yourself with citation software (I recommend Endnote);
- Learn to utilize the Styles feature in Word;
- Decide on a Greek font early, and definitely consider using Unicode (I recommend Gentium).

During your research:
- Consider scanning, rather than photocopying articles and other works, so you always have them on your hard drive (you can even save them as attachments on Endnote);
- Back up your work regularly (just email it to yourself if you must);
- Enter your meetings with your supervisor with a list of things to discuss;
- Turn in something, anything, for your supervisor to read every time you meet (this will provide you something concrete to discuss in every meeting and an opportunity for your supervisor to see/critique how you write and reason);
- Set deadlines for your work (I scheduled meetings to discuss my work with John several weeks in advance to give me a deadline to shoot for);
- Contact other departments within and without your university for additional insight (classics/ancient history, etc.).
- Study with others, especially those working on similar projects and utilizing similar resources (talking through your work with others forces you to clarify your own thoughts and assumptions).

After you submit:
- Get away from your desk and take a holiday;
- Medicate yourself to heighten your depleted immune system (if you work as hard as I did up to your submission date, your body will be more run down than you think and you may get sick shortly after, as I did).

I just happened to have an exchange with one of the publishers of PhDs.org, and I thought I’d pass their link along.  It’s US focused but it has several interesting and helpful areas.  One that I found most interesting was the Succeeding in Graduate School area, not least because they pull in links from articles that appear in various places.  Check it out.

As one of the primary preparations for a NT (or Patristics) PhD, I recommended focusing on primary text background sources.  I got an email question about which specific sources I would recommend, in order of importance.  These are the lists that I drew up.   Am I missing anything?  Would you recommend a different order?  Other thoughts?

Jewish*

  1. OT Apocrypha
  2. DSS
  3. OT Pseudepigrapha (esp. 1 Enoch)
  4. Josephus: Jewish Antiquities, Jewish War
  5. Philo: ???  (Recommendations on 2-3 works on where to start?)

*Need it be said that you read the OT itself first (possibly even from the LXX): Deuteronomy, Isaiah, Daniel, etc.?

Greco-Roman

  1. Cicero: De Natura Deorum, De Finibis (both read like a 3 views on theology and ethics, respectively)
  2. Plato: Timaeus, Phaedo, Symposium (longer works like The Republic will also repay attention given)
  3. Epictetus and/or Seneca
  4. Histories: Herodotus, Suetonius, Tacitus
  5. Homer (which was the “Bible” of Hellenism)
  6. Rhetorical handbooks by Quintillian or Aristotle

Mike Bird has a list here which has a similar focus, but also points to key secondary sources.

Christian

  1. Apostolic Fathers
  2. NT Apocrypha
  3. Nag Hammadi
  4. Justin Martyr and Irenaeus

Durham hosted a postgrad conference yesterday that was a new version of a ongoing tradition. For several years there has been an annual exchange between the NT areas of Durham and Sheffield. We alternated locations each year and had about 6-7 plenary papers, with a mix between postgrads and staff. This year, at the direction of Prof F Watson, it was opened to all Biblical Study areas, and Manchester was invited as well. We had 3 concurrent sessions with 8 postgrad papers each, mixed roughly evenly between the 3 departments. I had the honour of chairing one of the sessions, which had primarily NT papers. Manchester had a larger contingent than I expected, and Sheffield seems to weathered their potential shut-down last year well. I typically shy away from postgrad conferences, but almost all the papers in my session were excellent–interesting, clear, well structured, and, importantly for me as moderator, well within the allotted time limits. I will say that my opinion of Sheffield and Manchester was boosted by the event and my already strong opinion of Durham was confirmed.

Here’s an email I received from a prof at a former school. He captures an aspect that of the journey that I couldn’t express better:

A hearty congrats for finishing a long and arduous journey, of which few can fully understand. Family members are sympathetic and supportive but don’t really comprehend the gravity. Everyone says, “Well, we knew you would finish.” I also say that it is easy to be confident for someone else. The educational path you have taken is strewn with bodies of those who did not finish. Hurray for completing the road less traveled.

So this short post has now grown into 6, but hopefully some of you will find them helpful.

  • Formatting an argument.  I’m convinced now of a simple structure for abstracts, introductions, and proposals: context, problem, (hypo)thesis, and structure.  I preach this regularly in my classes and try to encourage others, particularly those writing proposals, to use this model.  Context: Give some detail about the big picture and about what people are saying about your issue.  Problem: What remains unresolved in contemporary discussions.  What question are you going to answer?  [Actually, clarifying and sharpening the question is,  I think, one of the most important parts of a project].  Thesis: what are you going to argue?  Obviously, you don’t always reveal this up front, but in abstracts, short essays, and proposals I often do.  Structure: Tell us how you are going to address the question.  The conclusion of many works just give these in reverse order.  It seems simple, even pedantic, but it clarifies things for readers, which is your primary goal.
  • Issues with writing multiple drafts.  Unlike shorter essays where you only make a couple of different drafts, each chapter will (and should) have multiple drafts.  Various naming schemes are out there, but I found the one that worked best for me was to just start at 0.1 and move up by .1 each time I made a substantive change.  E.g., Rom 8 0.1.docx, then Rom 8 0.2.docx, etc.  (If you do it by dates, you don’t necessarily want to update the file name for minor additions.)  Don’t ever label anything as ‘final’ until it literally is going out the door.  I’ve worked on projects with xxx final v2.3.docx, which is ridiculous.
  • Also, make regular backups of chapters and notes.  Computers break.  I kept all my thesis chapters and other works in a drafts folder.  Durham gives network space, and I found a computer program that copies the files from this folder to the network every day so that nothing was ever lost.  I also did periodic full back-ups to a portable hard drive.

In addition to my ramblings, I’ve secured word from my compatriot John Goodrich that he’ll also do a post (or more) on his thoughts about the PhD process since his project had some key differences from mine. Look for these over the next month or two.

I got an email from a friend asking me about time management during my studies, so I’m adding an extra post.  He noted that I mention the big picture–the 40 hrs per week–but how do you actually balance your time between reading and writing?  If you follow Mike Bird’s schedule, they’ll be no problem.  But for the rest of us mortals, it is an issue.

Like all projects, there is a need to balance research and writing in the thesis.  This is an especially difficult problem, because I found that I would much rather read than write.  In fact, deadlines were often the only motivator I had to actually force myself to start typing.  However, as it is often the case, once I started typing things usually began to flow because I learned that I write to think.  For short papers in seminary, I was able to bang out 5-10 pages based on basic research and what I already thought about issues.  But for longer, more complex issues and arguments, I found that I write to think.  That is, my thoughts become much sharper when I have to string them together on the page to make the argument flow.  Thus, I write first to think and then edit to communicate.  Talking through issues with others was also necessary for clarifying ideas as well.  Local dialogue partners are invaluable.

So how does that affect the actual writing?  I didn’t figure this out until after struggling to write my first full chapter (on Irenaeus).  This was the most difficult experience in the PhD for me.  I hadn’t settled in a study space, so I wasn’t putting in regular hours and so was scattered in my approach.  But importantly I also let the secondary research absorb too much time before I started writing and therefore was severely crunched for time when the deadline came close.  Here are a few ideas/habits that I did or wish I did:

  • Read and do your research on your primary texts first, and then write the draft of your chapter. That is, don’t engage with secondary material until after you get your ideas on paper.  This more than anything else will make your whole project easier and less stressful:
  1. You let your understanding of the text drive your discussion.  In a thesis you are required to detail all ancillary debates about issues.  If you do the secondary research first, your argument might get lost in these debates.  (I think this happened some in my Romans chapter.)
  2. This allows you figure out the parts of the text that need more thought, and thus it will help you better choose which secondary material to look at.
  3. This forces you to get the majority of your core writing done early.  You will thus have more time to edit and craft the flow than if you left the majority of the writing to the end.
  4. There are always unlimited amounts of secondary literature to read.  If you spend all your time reading, you won’t have time to craft your argument and your writing.  Clearly, there are issues that you will only learn about from secondary material, but let that come after writing the full piece based on the primary text.

If you do anything do that, but these are some other key aspects of getting things done:

  • Set out a timeline/schedule of your project, and give it to others to keep you accountable.  I had a chapter timeline, but each chapter ran at least a month longer than I planned.  I found that Barclay didn’t push me on timing and, in that way, allowed this to be my own project.  That is, I had to learn to set and meet deadlines.  Borrowing a practice I learned from Nijay, in my last few months I started setting weekly goals because I found it much more measurable and motivating than a huge ‘finish a chapter’ 3 months from now.
  • Schedule supervision meetings sooner than later.  These ended up being my hard deadlines for getting things done.  I often waited to schedule it once I was close to finishing, but this just let the timing for the chapter/section grow beyond its allotted time.
  • Plan to finish a week before the supervising meeting/deadline.  You’ll probably go over a day or two anyway, and you need to have time to proof read before submitting because you don’t want to waste supervision time with minor issues like spelling and grammar.

Those are some bigger picture aspects, here are some day-to-day practices:

  • Set aside the last (or the first) 30 minutes of every day to write 500 words.  If you did this you would have 90,000 words written in 180 working days (less than one year).  If you aren’t writing on your thesis, definitely write abstracts of what you read that day–thesis of the work, strengths, weaknesses, etc.  This 500 words could easily be a blog post.  Thus, you could get double benefit–summary/response to a work and some name recognition in the blogosphere.
  • Another aspect of daily time management relates to studying in community.  My time was greatly, immeasurably even, enhanced by my studying in the 37 N. Bailey office.  I had great discussions that sharpened my thinking, often by challenging my approach.  However, coffee breaks often went from 15 min to 45, or lunch from 1 hr to 1.5 hrs.  It takes discipline to walk away from fun conversations, but you can easily lose 1-2 hrs per day from too much chatting.  In my last 6 months I move to a different office, at first because of boiler work being done in 37, but I later stayed in my new digs because I needed the solitude that it offered to finish.  It’s a difficult balance, but most seem to do fine with it.  For those without kids they can make up reading at home, but for me 95% of my work was only during office hours, so I had to guard that time.

Daily time management and procrastination can be difficult problems for large projects with only generally defined deadlines.  Hopefully some of these ideas will be of help.

Finishing

  • I never finished drafts of my chapters in time to have someone proof them before I turned them into Barclay for our supervision sessions.  That isn’t something I’d recommend.  At the same time, it also takes a committed friend to read things in a rush like that.  However, I highly recommend having someone read the whole thing at the end.   Kevin Hill did this for me, and he helped polish the work to make it much cleaner. I’m returning the favour when he submits.
  • The thesis is never perfected, but eventually you have to turn it in and be done with it.   Francis Watson passed on to me what Andrew Louth told him while doing his PhD: ‘Theses, like all monographs, are never finished; they are just abandoned’.  Similarly, this is another point of view I heard: This is just a driver’s license.  Get your license and move on!

Viva

  • The best advice I had to prepare for the viva, other than rereading your thesis, was to read through the works of my two examiners, especially book reviews they’ve done because you can see how they assess various arguments.
  • Other things I did was to bullet point answers to these questions: can you summarise your thesis, what are your main contributions, why did you choose this methodology?

In case you are interested these are the 6 primary questions that are posed to examiners at Durham:

  1. Has the candidate shown that he or she is able to conduct original investigations?
  2. Has the candidate shown that he or she is able to test his or her own ideas and those of others?
  3. Has the candidate shown that he or she understands how the special theme is related to a wider field of knowledge?
  4. Does the thesis contain an original contribution to knowledge?  (The thesis should include matter worthy of publication though it need not be submitted in a form suitable for publication)
  5. Is the style of the thesis satisfactory?
  6. Is the presentation and general arrangement of the thesis satisfactory?

During the PhD
Technical Stuff

  • I used Endnote back from my days at DTS.  It was so easy to just continue it all the way through.  I tweaked the format along the way to get it how I liked it.  When it came down to the final draft, I just hit update, and I didn’t spend more than an hour looking at it at the end.  Endnote is not perfect, but it’s usable.  If you don’t go with that, get something.  However, I don’t highly recommend NotaBene.  Wright uses it, and I’ve found aspects that just aren’t helpful.  Also, the world revolves around Word, anyway.
  • Speaking of Word…Make use of its ‘style’ feature.  I set two paragraph styles–indented and not–and a block text style.  In addition, the headings are great.  If you use headings, you just click update and voila the table of contents is exactly as you need.  Plus, it helps if you need to make a change to formatting of text, etc.  Just make a change to the style, and everything is changed.  I have a friend that used specific styles for his Greek, Hebrew, etc. so if he wanted to change the font all the way through it was no big deal.
  • Speaking of fonts.  I did’t have to worry about that because I use Unicode.  Again, do this from the beginning, and your life will be easy.  I use gentium, but once SBL combines its Greek and Hebrew unicode, I’m sure I’ll move to it.  Plus you can get the cool text critical symbols easily.
  • Online Backups.  With graduate studies, having a secure place for your documents is necessary.  I’ve had a couple of hard drives go out since I’ve been here, but I was fortunate that I never lost anything.  There are a couple of programs that I’d recommend.
  1. Dropbox is a must.  Basically, you get 2GB of (free) online storage, but the files also stay local on any machine you download the program to.  That way, you’ve always got access through the internet or on any computer with the program (each computer has the same folder in the My Doc folder).  So, there’s no more emailing files back and forth, and you’ve got an online backup for key documents.
  2. For  backing up the whole hard drive, we use Carbonite.  It makes a full back up of the whole drive, and then it automatically recognises when a new file is added or if a file is changed and backs those up.   It doesn’t do everything I’d like (it’s limited to one hard drive per subscription), but I never worry about pictures and work files being lost.

During the PhD
General Stuff

  • The best description of the PhD process that I heard from somebody is that it is often ‘non-linear’. That is, you don’t always neatly progress from one section to the next. Sometimes you try out ideas, explore avenues, and they just don’t turn out. So, then you try out others.
  • Treat it like a job–work 8-5 daily, or whatever works for you to get at least 40hrs/week.   I was much more productive when I got out of the house and worked at the same study area daily.  That being said, I found that I wasn’t as productive during term time because of all the extra bits that go on: weekly NT Research  Seminar, weekly Patristics Research  Seminar, leading undergrad seminars, marking essays.  The first year is especially busy as you attend Latin/German reading classes and audit a couple of MA modules (as is expected for most).
  • Thanks to Nijay, I had a lot of encouragement to not only attend conferences but to also to present papers right from the beginning.  I’m not as good with small talk like Nijay, but by presenting and interacting you are able to meet people and make contacts.  For instance, I importantly met Mike  Gorman at SBL my first year and learned that we have significant overlap in our interests.  We’ve had a good relationship since.  As another example, I presented my methodology at the British New Testament Conference, and Mike Bird heard me and learned about my interest in Irenaeus’ use of Paul.  As a result of that, he later asked me to contribute to a collection of essays on Paul’s reception in the second century.  It’s an honour to be included in the work, and it all came out of something that didn’t take much extra work.  Plus, by presenting you get good feedback and learn to discuss ideas before the viva.  The BNTC is great because it’s always <200 people, so you get to rub shoulders with most of the British scholars easily.  Plus you all each common meals, so there are even more opportunities to meet people.
  • Blogging…I’m not sure I would recommend trying to start a blog by yourself.  You see my trouble in keeping up regular posts.  However, I think I have reaped huge contact and name recognition benefits by having one.  While lists of blogs are always growing, if you have one that is updated regularly (at least once a week) then it can help you meet and interact with others.  I would recommend joining with one or two others and doing a group blog.
  • I found the research seminars were great for exposing me to various areas of the general field.  (As a side note, always dress a little better when you go to seminars than just jeans and t-shirt.  I’m a firm believer that people judge you by your dress and treat you accordingly).  At the same time, I would have picked up major works, especially those outside my area of study, earlier and just read intros and conclusions to get a feel of the lay of the land outside my topic.  I’m a religious reader of RBL, mostly because I can get it on my blog reader.
  • An easy way to keep up with stuff is by doing book reviews.  Again, Nijay is the master of this and he passed along his wisdom to those of us who shared an office together.  Free book, extra knowledge, what’s not to like?  The problem I found is that they just take up so much stinking time.  You don’t want to do a sloppy job because it reflects on your scholarship, and the publishers get all the reviews and send them to the authors.  (So, don’t be too negative because they will read it, and who knows they may end up being an external examiner!)  Also, think about the relative value.  With regard to time, 15 or so reviews = 1 article, but with regard to employment, 15 reviews carry no weight at all, though a peer-reviewed article definitely does.  So, I quickly limited myself to 1 review per quarter unless the work was central to my thesis.
  • Get something accepted for publication before you finish, hopefully before you start applying for jobs.  Most schools don’t care if you publish sections of the thesis beforehand, and it just goes to support you in your viva.  I published something that was central to my thesis, but I didn’t have the word-count space to develop it.  My first and only article started as a BNTC paper a couple of years before, and I just let it simmer until it was ready to be published.  Since this is such an important part of academia, I devote 1 night per week for journal work/conference papers, in addition to my normal schedule.  That way, no matter where everything else stood, I knew I’d get something done on the article.

« Previous PageNext Page »

Follow

Get every new post delivered to your Inbox.

Join 217 other followers