One of the nicest things about graduate school, for me, is the control over my schedule. I had that in undergrad too, but more constraints because of more classes. Also I was still riding horses almost every day, which cut out most evenings. Why is control over my schedule so great? Because I am obnoxious about my work habits and I think I can get better work out of myself when I follow my nose.
I drafted this post a few weeks ago in a fit of inspired work time. (I’m still just as excited about knitr, by the way. And the paper I mention is getting submitted in the next week or two, with full data and the code formatted all pleasantly thanks to knitr.)
You guys know the way I think about work habits all the time: I have detailed writing strategies, I enjoy settling into routines and then semi-frequently breaking them, I spend time thinking about nature of motivation. About the only thing that stays really constant is that I’m a morning person, so I don’t really do work past 7pm except in dire circumstances or…moments of pressing inspiration.
Which is to say: yesterday I was working on R code for a really neat project on horses from the Paisley Caves of Oregon, and as I was working I was pondering its eventual inclusion with the paper itself. So I was trying to be thorough, you know, including code to save the plots and commenting things nicely and such. And then I thought, what the hell, learning to use knitr and rmarkdown to make nice outputs has been on my to-do list for awhile, let’s learn it.
Alright, well. I guess now is as good a time as any to get around to learning knitr and associated fun.
— Fossilosophy (@fossilosophy) October 23, 2014
Which is more or less why I wound up working last night until about 8, when the grumbling of my stomach became too much to ignore. (You’ll note that the other half of Fossilosophy would snicker at this, as Kelsey sometimes doesn’t even warm up until around that time in the evening.)
Because I was having fun. So much fun. Do you guys REALIZE how cool knitr is??
Right, about priorities: yesterday I tasked myself with working on writing mammalogy labs. That is also a cool project that gets me really excited about science and teaching, because I get to design an entire semester’s worth of labs. And also I am feeling internal pressure to make forward progress on it because it has slipped down on the priorities list thanks to preparing two posters for SVP.
But I was really excited about knitr!
So you know what? I worked on my code and knitr. Because damned if I’m going to waste the kind of excitement that helps me learn important tools I’ll use in just about every research project ever, while also moving forward the project that is probably closest to submission of all my projects.
This is the glory of having few to no hard deadlines this semester, a luxury that I recognize is rare and thus will milk for all it is worth. I will still write all the mammalogy labs; a day or two will make zero difference. How silly it would have been to let the internal guilt meter decide what to work on when I was truly excited and motivated about something else that also offers me long-term research benefits.
Extra credit links:
A Beginner’s Tutorial for knitr
Knitr with R Markdown
Getting Started with R Markdown, knitr, and Rstudio 0.96
Drifting towards deadwood, or not: learning to use R (interesting thoughts on putting in the time to learn big new skills; same thought process I use to make myself put in the time to learn things like knitr)