The Hammer Falls...
Sunday, February 27, 2011 at 10:20AM To anyone outside of the Ivory Tower many of the posts on my blog probably make it seem as though academia is a complete mess. Unfortunately, this is at least partially true - standards of achievement vary wildly among institutes, departments, and even individuals. Ask any number of professors what you should be striving to accomplish as a wannabe professor and they're likely to give you a substantial number of different responses (some aspects, e.g., work hard, publish good papers, etc. tend to be invariant).
A good example of this is the very act of postdoc-ing: What should an interested, newly minted Ph.D. be looking for in a potential postdoc? What should a new postdoc be trying to accomplish during their tenure? On these subjects, as above, I've gotten a few different responses.
One popular answer to the former question is that a postdoc is a time when you should be 'consolidating' your interests into a viable research program. Basically, you should be focusing on publishing some big papers in your field of interest that will get potential employers interested in hiring you to pursue your work with a lab of your own. I've been told that in order to accomplish this goal, you shouldn't enter a postdoc that involves too radical a shift away from the skills you learned during your Ph.D. - that is to say, don't start doing something completely new1.
On the other hand, there have been a few folks who opined that a postdoc is an excellent time to diversify your skills. Also withing the confines of this view, I was told that the postdoc is the best time to be a scientist: You're much more independent (and well-trained) than most graduate students, but you're still free to pursue your own research, free from the later demands of writing grants and running a lab.
While I see some of the wisdom in the second perspective (I have certainly learned a ton of stuff in the ~16 months of postdoc-ing I've done), I have to admit that 'mine' own experiences are probably more in line with the first one. I'm way too busy as a postdoc to spend any significant amount of time improving my skills in areas that are not directly related to my research. I've always got at least 3 projects on the go involving significant time investments, and almost everything I've been doing has clearly defined deadlines - Our lab is involved in the Drosophila ModENCODE Project, which involves a large consortium of labs and thus deadlines are inevitable. When the hammer falls and deadlines loom, the practice of science changes radically: No longer is it the purely intellectual journey of discovery, but rather the focus shifts to determining 'deliverables' and getting s$%t done, ASAP. I'm in one of those periods at the moment, unfortunately.
The funny thing is that, while I'm learning a ton of stuff during my postdoc, I tend to feel that I have less time to reflect and absorb said knowledge than I did during my Ph.D. For instance, during grad school, I began creating text files, wherein I would type summaries of new computational techniques I'd learned that would be useful in subsequent analyses (I had a file on Linux commands, a file on R, a file on PERL, etc.). While I still refer to these files daily, I find it difficult to expand them with the new information I've gained. I'm typically running through analyses so quickly that I don't feel like I have time to explore all of the details of some of the software I use - much to my chagrin2. I've kind-of resolved myself to take a little time here and there to beef up my text files and if I can get them all nice enough, I may even post them here on my site.
Oh well, what else is new, right? I began this post by remarking on how opinions about what I should be doing vary, however, it's pretty clear that the current consensus is somewhere along the lines of 'work your ass off, publish as much as possible, make sure people know who you are.' I'm sure that other people's experiences are different though. If so, I'd love to hear about them!
P.S.: I would like to give a shout out to looniechemist, who runs the blog 'An American postdoc in Canada' and who wrote an interesting post about her early experiences as a postdoc that got me thinking about writing this post.
1For instance, my Ph.D. was a pretty radical departure from the sorts of skills I learned during my undergrad and Masters (I switched from Biochemistry to Evolutionary Biology). This led to me essentially 'burning' a year in order to bring myself up to speed in the field - something I don't regret in the slightest. On the other hand, burning a year as a postdoc is potentially devastating.
2I think that this has serious implications for the quality of science produced using certain types of software, and I'll expand on this in a future post.
Carlo |
2 Comments | 



