Thursday, March 6, 2008

Production is up!

I had a small breakthrough today. I took some advice from How To Write A Lot and ended up writing a lot this afternoon.

First, I got permission to turn off my internet connection and did so for several hours. It made a huge difference, even though I could easily turn it back on when I wanted. When I'm working on data analysis or writing, I often briefly check my email whenever I get to something that requires a little thought. Not having that option really kept me on task.

Second, I re-read the bit about writing introductions. Silvia recommends a three-section template for intro's: stating the problem, expanding on the problem, and stating how the present study will address the problem. This sounds so simple it's verging on silly and of course the advice in the book was more elaborate. I have always struggled with intro's because I have a hard time seeing them as a whole. I can write good paragraphs presenting the relevant ideas, but I have trouble organizing them in a logical structure. I shuffled around some text I already had and then wrote some more. I think my draft is much better now.

I told Academic Advisor that I would be giving the lab group a draft of my manuscript on Tuesday so we can discuss it at lab meeting the following Tuesday. I think I really need a deadline goal. Undoubtedly, it will also be extremely helpful to get the comments of all those readers, even if they don't read it very thoroughly (which I doubt they will).

Wednesday, March 5, 2008

Finding the good in the boring

Today I went to what I thought would be a professional development seminar but it ... wasn't. It was a presentation utterly irrelevant for me and I don't mean it in the I'm-too-cool-for-this-seminar-because-it's-not-quite-in-my-subfield sense. This presentation just had nothing to offer for me. I guess I did learn that there is a group that sometimes engages in professional development activities. Also, I got free pizza.

Aside from the pizza, I got a reminder that my research is cool and important. Lately, I've been feeling like my work can't possibly solve the problems it's funded to solve and it's all a farce. Sure, the research we do to address programmatic goals generates new and vital information. But in some ways, the programmatic goals are a little stupid. Anyway, I was sitting next to this guy who wanted to chat so he asked what I do. He was enthralled as I explained my research. He had heard a little about the topic in the media and was interested to meet someone actually working on it. He asked all these great questions and appeared to be genuinely intrigued. His research, theoretical physics, was so far from my expertise that I could barely ask any questions at all but he didn't seem to mind. He told me how cool it is that my research has real world applications that are meaningful to society since his apparently doesn't.

What a wake up call. I was just last week feeling like I want to branch out so that my work has more applications that are meaningful to society.

It's all relative.

Tuesday, March 4, 2008

Student vs Employee Part 2: Work Hours

One of the perks of an academic job is the flexible schedule. That creates ambiguity for students, who may not know the expectations for grad student time. It seems that many advisors are reluctant to directly address the questions: how should a grad student define her/his work schedule? How much work is expected? Do they get vacation time? Sick days? Comp time?

Typically, if you have a job at an organization as large as a university, the HR department controls your compensation, including schedule and fringe benefits (at least I think that’s how it works since I’ve never had a regular job!). But grad students fall through the cracks and it can be confusing.

As I’ve said before, I spend most of my time at a place outside the university, so I work among people who have regular 40-hour work weeks. I feel like an ass if I’m not there approximately when they are even though my status and compensation are totally different. So I work 40 hours/week plus some weekends and figure I’ve done my duty*. I figure I can take 2-3 weeks vacation each year (including the winter holiday break but not the holidays themselves) and if I want more than that, I need to make up the time by working nights and weekends. Actually, I probably work enough beyond my regular 40 hours to make up at least part of those 2-3 weeks without tracking it. I do not log sick days, but I don’t take many of those.

It’s different in a university setting because people are off doing all sorts of things that make them absent from the office/lab. Students are teaching or taking classes, faculty are teaching or in meetings. This makes it easy for people to breeze in and out with little accountability for their time. I have no doubt that many academics work an obscene number of hours. But I also suspect that many students (and faculty for that matter) would be surprised by how little they work if they actually clocked their time spent really working.

The tricky thing is that students don’t really have to work any set number of hours. Their TA or RA is probably for 50% time, which is pretty unclear since they are obviously expected to work more than that. Nobody tells incoming students how much they should work, so some treat it like undergrad, showing up for class and doing everything else at home. Others, like me, treat it like a job, which may inhibit their progress. And of course, work hours are a central source of conflict in many student – advisor relationships.

Just one more thing that new academics are stuck learning for themselves. How many problems could be prevented or solved by just telling people what they need to know?

*This is largely to deal with guilt about not working all hours, i.e. if I work hard during normal hours, any extra time is bonus.

Monday, March 3, 2008

Oops, brain fart!

I forgot to call out the March anniversary edition of Scientiae. If you haven't yet, go check it out at Rants of a Feminist Engineer. Skookumchick did a bang-up job compiling the carnival!

NYR February Review

Another month has breezed by; it's time to check in on my New Years' Resolutions.

Project Efficiency has gone downhill. I haven't been writing daily goals, which is the centerpiece of the program. I have also been checking my bloggy email and maybe sometimes peeking at bloglines during work. On the other hand, there hasn't been a lot of fake working. I think I can be proud of that. I'm optimistic about March after reading Silvia's book and getting Slimtimer. So my goals for March are to get in the habit of actually using Slimtimer regularly while establishing a writing routine.

Money went pretty well in February. In addition to the normal big-for-my-income sum that gets automatically transferred to my ING savings each month, I had a little bit leftover on the 29th to add to the kitty. Having two international trips planned really motivates me to save. In other news, Psycgirl and I are thinking about starting a multi-author blog (similar to the Active Academic ) to discuss all manner of money issues that academics have. Anyone interested in that?

We cooked most of our dinners, but there was more pizza than there should have been. Oh well, it was yummy.

Work has been medium. I made some more progress on Chapter 1 paper and discussed what I have so far with both advisers. There's still a lot to do though. There was a little progress for Chapter 2 as well, as I had to complete the final laboratory analyses on one chunk of samples and partially work up the data for a conference abstract. My goal for March is to finish a complete, decent draft of the Chapter 1 paper.

Overall, February was medium. I'm hopeful that the longer days of spring will revitalize me. But, who am I kidding? It won't be spring around here for another two months. I guess I may as well be working!

Sunday, March 2, 2008

Writing a Lot

Yesterday, I went to this very cool new coffee shop around the corner and read Paul J Silvia's How to Write a Lot in two hours and ten minutes. Loved it. The book basically explains how to pull your thumb out and get your writing done by sticking to a schedule. Other bloggers have reviewed the book more thoroughly, so I won't do that here. I will say that my favorite aspect of Silvia's advice is that if you have a writing schedule and stick to it, there should never be any guilt or anxiety attached to writing and you won't feel like you should be writing in your free time. This is my kind of advice.

I usually get to work between 7:45 and 8:15. Other people in the lab roll in between 9:15 and 10:30. Typically, when I get to work the first thing I do is check my email while eating a portable breakfast (granola bar or english muffin). I also go through journal TOCs and download relevant articles. I could, however, easily schedule my writing time for 8 to 9:30 or 10 am. I could get to work and start writing right away, saving my email stuff for after writing time. I could keep my door closed during this time for extra focus, although few of my coworkers would be there to interrupt me at that time anyway. Plus, I would have the whole rest of the day for lab work. That would relieve the daily dilemma about whether to do labwork or writing.

Silvia also recommends a way to keep track of progress using a spreadsheet (not particularly novel but helpful nonetheless), which is cool since I was wondering about that recently.

I can't wait to get started with the new system. I think it will mesh well with my new work timer.

A monster in my midst

I am quite certain that there are no beavers around here.

What the hell is eating this tree? Squirrels? Gremlins?