Tuesday, September 30, 2014

The sorrows of peer-review: now less sorrowful

At long and painful last, that article I wouldn't shut up about has been accepted. As I've mentioned, this is the most difficult experience I've had getting something published. Some of that is just the random luck of the draw, but there may also be specific reasons this was such a tough sell.

First, it's on Shakespeare, on a hyper-canonical play, and it deals with some touchy political material. This means, on the one hand, that there are more people in the world with investments in the material than is usually true for the texts I write about, which perhaps makes pushback more likely. On the other hand, since it isn't my primary area of specialization, it's possible that I initially framed my argument in ways that struck others as naive--or that were only aslant or adjacent to the important existing critical conversations.

I do think that earlier versions of my essay were worthwhile and publishable--and that a few of the objections I got were unreasonable, not to say batshit crazy--but my last round of revisions really did lead to a mini-breakthrough, allowing me to synthesize two strands of argumentation whose relationship I had never previously been able to articulate. And doing that led me to a major realization about the argument of my second book.

So though I'm on record as hating the cult of "it was all worth it" and "now I'm so much better off," what with their haste to deny the lived reality of suffering and suckitude, it's also hard to regret that things turned out this way. That, I guess, is a larger motto for this blog: insisting on the shittiness of the past doesn't mean wallowing in that past--or denying its utility. Sucky things can make you stronger (and lead to non-sucky things), but they still suck.

(That's why you read my blog, right? For these philosophical gems?)

Anyway, as reminder and reality check for Older Flavia, when she's agonizing over the long gestation period of some future project, I thought I'd detail the timeline of this one--an article of not even 10,000 words--from conception to acceptance.

Spring 2010
Notice a Thing
Run a quick MLA database search
See that someone Noticed my Thing 40 years ago and wrote a few paragraphs about it.
Boo: I'm not the first! But yay: no one's done anything interesting with it!

Fall 2010
Accepted to a relevant-sounding SAA seminar
Spend a week doing enough research to write a 500-word abstract

February 2011
Spend four weeks doing increasingly desperate research into increasingly esoteric fields
Cobble together 3,000 words for a speculative seminar paper

April 2011
Receive a lot of enthusiastic seminar feedback
Someone I know slightly buttonholes me and tells me to publish it immediately.
GAAAAAAH. Like hell.

February 2012
Admitted to a very different SAA seminar
Intend to do a ton of new research; instead just write a new introduction and conclusion.
Decide this framing opens up the topic more fruitfully

Summer 2012
Do my literary-critical due diligence
Email strangers begging for evidence of what I feeeeeel to be true
Spend six weeks writing
Submit resulting essay to a journal

Fall 2012
Receive two readers' reports: split decision
Journal requests a revise-and-resubmit

Winter 2012-13
Revise
Resubmit
Rejection

Spring 2013
Submit to a different journal

Summer 2013
Another split decision, but this time with a very encouraging editor
Revise lightly and resubmit

Fall 2013
Unhappy reader still unhappy
New third reader has useful and targeted suggestions
Ambiguous communication from editor suggests he wants another revise-and-resubmit

December 2013
Do a shit-ton of new historical research
Majorly restructure essay
Resubmit
Oops: turns out that ambiguous communication was a rejection!

January 2014
Decide new version suits a journal I hadn't considered before
Submit
Desk-reject within two weeks (guess I was wrong)

February 2014
Submit to a fourth journal

April 2014
Receive two exceptionally helpful reports
Find self--nevertheless--demoralized by another R&R

April, May & June 2014
Avoid working on essay
Weep whenever I think about it

July & August 2014
Revise with excruciating pain
Send revisions to a friend
Receive new & different set of ideas for revision
Weep some more
Realize two of his suggestions might solve my most intractable problem
Revise some more
Resubmit

September 2014
Acceptance!
. . . .
. . . .
. . . .
. . . .
Wait, that's it?

Astonishing how something can be such a relief, and so anticlimactic, at the same time.

Friday, September 26, 2014

The humanities post-doc

In the comments to a previous post, Random Grad Student asked for my thoughts about the humanities post-doc: "its place, how to get one, [and] how search committees at different institutions view them when you're applying to a tenure-track job."

I admit that I have little experience with these. They were starting to proliferate when I was first on the market ten years ago, and I now know a number of people who have held one--but though I recall investigating a few, I never seriously considered applying. It may just have been that none of the topic-based post-docs fit me that first year (and my second year I was in a good renewable lectureship, so I didn't look at anything non-TT). But I think it mostly struck me as pointless work, on the front end, while one was also applying to tenure-track jobs.

(I still think this; I understand why post-doc applications are due early, but since every job placement officer I've ever met considers a post-doc inferior to a tenure-track job, it might be more sensible for them to list in the spring, along with VAP and other non-TT jobs.)

So with that proof that I don't really know what I'm talking about, I'll say what I do know and have seen, and hopefully my readers will pitch in more knowledgeably.

1. How To Get One: no clue. (Readers?)

2. How Search Committees View Them: I don't think that, at my own institution, we particularly distinguish between post-docs and VAP or other full-time non-TT employment. We're looking to hire people who have a couple of solid publications and some directly relevant teaching experience, so if a post-doc gives you whichever of those you need, that's great--but there are other means to that end. Indeed, for our purposes, a fancy post-doc might not help a candidate coming from a fancy institution if his weakness is precisely his lack of bread-and-butter teaching experience.

Research institutions might feel differently, but my sense is that even they aren't specifically excited about a fancy post-doc unless

a) it's the most fancy (by which I basically mean the Harvard Society of Fellows)

or

b) it gives you something you don't already have on your vita

Again, this is just my impression, but while there are lots of reasons for a candidate himself to value the opportunities provided by a fancy post-doc--research time, new professional connections--I don't think that, simply as a line on the vita, it adds much to a candidate whose degree is from an elite program. But for a candidate whose degree is from a second-tier institution, then that Mellon-funded post-doc likely does act as an important additional accreditation.

None of this is to malign the post-doc; it's a nice line for anyone to have, and preferable to continuing to teach at your grad institution (and certainly better than taking a VAP with a heavy teaching load or adjuncting). And used well, it can help you add other things to your vita and application materials.

But my feeling is that it's a shiny consolation prize for those who weren't able to find (or weren't looking for) a TT job the previous year.

As always, readers, I trust you to tell me how I'm wrong.

Wednesday, September 24, 2014

Four on the floor

So I'm taking that conversational Italian class after all. The catalogue description says it's open to anyone who has completed at least a semester of college-level Italian, but it's clearly imagined as serving Italian minors who want more speaking practice (and who are taking the course alongside a grammar or literature class).

For the first two meetings there were seven of us plus the instructor, and I was happy to note that my skills placed me roughly in the middle: there were a couple of minors who were better than everyone else, but there were also people who had only taken a couple of years of high school Italian or whose first exposure to the language was a semester or summer in Italy. Some had great accents and were prompt with basic constructions, but had limited vocabularies and didn't know much complex grammar; others were terrible, awkward speakers who--it soon transpired--actually knew a tremendous amount.

Then three people dropped. And with just four of us. . . well, my oral and reading comprehension are on a par with my classmates', but my verbal fluency is probably the weakest of anyone's. Extemporaneous speech has never been my strength, and even in English I'm prone to blurt and babble. But at least in my native tongue it's only the content that's insane. In Italian my mouth will just randomly produce the wrong phoneme or scramble a verb tense beyond all recognition. I make an ass of myself twice a week. It's awesome.

But this isn't really a post about that. It's a post about the four-person class, which this semester I also have the pleasure of teaching.

It's possible, I suppose, that a four-person class could be terrific, but it strikes me as a uniquely bad number: just big enough to be run as a regular class, but not big enough for it to work. Individual tutorials would be easier, since those can be adapted and adjusted to each student's needs and abilities. With four people, though, each student bears somewhere between three and ten times the responsibility that she would in an ordinary class--and unless all four are at the very top of their game, there are going to be problems. In my own seminar I find myself lecturing more than I do with a class of thirty, simply because I need to give my students a break.

The only upside is that I've been learning from my Italian instructor. Although our classes are very different, she's clearly having some of the same struggles, and handling them better. She's been mixing things up, trying different strategies, looking for what works.

Whenever she figures it out, I'll have it made.

Monday, September 15, 2014

Job season round-up

Since the MLA's Job Information List went live last week--and since I apparently have nothing new or interesting to say just now--I thought I'd collect in one handy location my musings and bits of advice from years past:

Why you should stop freaking out already about whether a particular job has an inside candidate.

How to be competitive for a "middle-class job"--that is, the kind of place that values teaching and research about equally. (Somewhat related: ways of parsing the differences among institutions, beyond looking at teaching load.)

What not to sweat about the conference interview.

A peek (or two, or three) into how the job search feels to those inside a hiring department or committee.

And just for fun: why the job list still fascinates and unsettles me, every damn year, whether I'm applying or not.

*

Looking through the posts I've tagged as "The Academic Job Market," I see they provide less concrete advice than I'd thought. Other bloggers have covered a lot of this ground before (last year, Notorious Ph.D. wrote a series of posts about the component parts of the job search, and the year before, Bardiac did the same)--but if there are any topics my readership would like to see me tackle, leave a note in the comments and I'll see what I can do.

Good luck out there, kids. We're pulling for you.


Wednesday, September 10, 2014

PSA, maybe

So, that problem of needing access to scholarly databases to which your institution doesn't subscribe? I may have found a solution.

Register as a nondegree or nonmatriculated student at whichever local institution does subscribe. Obviously, not all universities permit students in this category--I imagine you can't be a nondegree student at Princeton--but plenty of places whose mission involves the surrounding community have programs that allow random citizens to take a class now and then on either a credit or audit basis. And in my experience at two institutions in two states (Cosimo's public R2 and now a private R1), all you have to do is fill out a quick web form, wait a day or two for approval, and then you get a student ID number and login.

And that gives you library web access.

Now, I can't promise that every institution would give you library access without your actually enrolling in a course--or that such access would last for longer than a semester or two--but in both the places where I've been a nondegree student, web access to everything was immediate, and not a function of being enrolled or paying one red cent.

I leave it to the enterprising among you to conduct further research.

Sunday, September 07, 2014

Modeling

I spent my Friday night writing a model close-reading essay for my Milton students. This is the kind of thing I always think about doing, but almost never do--just because it's labor-intensive and annoying and because I spend enough time on class prep as it is.

Since virtually all my classes require some understanding of the terms and techniques of formal poetics, the close-reading essay is one of my staples. In Shakespeare I have my students close-read a speech in verse, and in my other classes I usually have them do a sonnet. Since my own college teachers did a piss-poor job of teaching poetics, I've spent a lot of time thinking about the basic toolkit students need to understand and analyze a poem. And I gotta say: I love doing it. Even after years of assigning some version of this essay, I'm still not tired of it.

But not being tired of it isn't the same thing as saying I've done everything possible to prepare my students for the task.

Sure, we do a lot of close-reading in class, and I try to be explicit about how our work might translate into a thesis or how we might organize all our observations into a coherent argument. And I've revised my assignment sheet a number of times to include a detailed breakdown of the whole process. But as for an actual model. . . eh. A couple of times I retyped one of my own undergraduate essays to share, and often I kicked myself for not having been foresighted enough to ask a student from a previous class whether I had permission to distribute copies of her paper. But I could never fathom finding the time to produce five relatively polished new pages of my own.

But this week I decided it was time. Maybe being on sabbatical last year left me with secret reserves of pedagogical energy, or maybe it's just that I've taught for long enough that the basics of class prep don't suck up as much time as they used to. In any case, I sat down and banged out a four-page close-reading of Sonnet 7 in a little under four hours. (I ask that my students' papers be 4-6 pages--and true to the undergraduate spirit, I decided there was no benefit to my doing more than the minimum.)

And you know what? It was fun. Maybe not the funnest thing I could have done on a Friday night, but it wasn't bad. I don't think it gave me any new insights into the assignment itself or how I might do things differently in the classroom, since I've been tinkering with those things for years. But it did produce one or two new thoughts about a poem I thought I knew upside-down--and there's ultimately no substitute for showing students how a thing is done, even when you believe that your instructions are perfectly aligned with both the process and the end product you desire.

Also? I won't have to do this again for years.

*

Readers, when have you gotten into the trenches and done an assignment alongside your students? Did it change your teaching or the nature of your assignment?