Logging my time (Week three of Spring Semester 2018)
About a week ago, I reported on my time log for the second week of spring semester. In case you’ve forgotten, the College now seems to care about how I divide my time during the summer , so I’m now trying the experiment of recording my time during each week of the academic year.
During that week, I spent sixty-six hours on work-related
stuff. I thought that was too much. During week three of spring semester, I found time to go out to Andi Tracy’s
learn about your tastebuds event and to spend most of a day following Youngest Son to activities. But I also worked. A lot. As far as I can tell, I spent about seventy-five hours on work-related activities. That’s not reasonable.
Where did the time go?
- I spent nearly fourteen hours on activities related to my role as SIGCSE Student Volunteer co-Coordinator. Most of that was dealing with smelly code  or trying to set up a 200+ line spreadsheet of activities that need student volunteers .
- I spent a bit over ten hours on electronic mail. That’s up two hours from the previous week. It may be that I was less good about doing specific categories of email in sequence, and so things I previously logged as
CSC 151were logged as just
- The amount of time I spent on my classes went down slightly. I spent over ten hours on CSC 32x and almost eleven on CSC 151. But that doesn’t count the small emails, the office hours, and probably some informal conversations.
- I spent nearly five hours on research, mostly working on a presentation.
- Almost all of the other time was on assorted work or administrative stuff: Meetings, preparing for meetings, paperwork, office hours, and so on and so forth.
- I spent almost six hours musing. That’s how much I mused the previous week, too . Should I count musing as
hobbyor …? For now, I’m counting it as
I definitely need to find things to cut. I’ve been spending way too much time on the Student Volunteer Coordinator role . Fortunately, SIGCSE comes soon and, while I’ll spend even more time during SIGCSE working on SV  stuff, after the conference my tasks are mostly done .
I should look for a way to spend a bit more time on my classes. I’m guaranteed to spend more time this week: I have a CSC 151 exam out, and that means that I’ll be spending much of the weekend grading . I also have the CSC 322 mentors on campus this week and will be spending time with them. But there are other class-related activities I’d like to be doing, particularly catching up on some past grading and some new prep.
 Or at least about how I divide my time between activities for which I receive pay. They may also care about what percentage of my
work time the paid activities occupy.
 Software designers talk about
code smells. Code smells are usually bad. I may muse about the code smells I dealt with.
 By the time I got to line 120 or so, I figured out how to automate part of the process. But some things still had to be done manually. Then I had to go back and add a bunch of other events that were not in any of the data sources I had to work with.
 I did not count the musing hours in work hours. I worked seventy-five hours and mused for six. In some worlds, that means that I worked for eighty-one hours.
 I’m trying to decide whether or not to be happy that I did not log the SIGCSE work in December and January. On one hand, it would be nice to know how much work I really did. On the other, it would likely also be very sad. I do know that, to date, I’ve dealt with about 900 messages related to SIGCSE.
 SV is short for
Student Volunteer. But you probably guessed that.
 Oh. Wait. I think we have a responsibility to report session counts for every conference session. And, um, tell the registration folks which students actually worked their shifts so that we can refund their registration.
And I should probably rewrite the bad parts of the code now, when it’s fresh in my mind, rather than when I’m back in panic mode.
 Or another musing.
 What meetings did I do last week? A PossePlus discussion. Faculty Fridays. Faculty meeting (and some prep). The Faulconer Advisory Committee. A department meeting. CS Table. CS Extras . A few others I won’t record in a public forum. Yeah, my meetings might make a good topic for a broader musing.
 Does that count if I was presenting? Since I try to attend each week, I counted it as department work. I suppose I could have counted it as research time.
 Six problems per exam. Five minutes per problem. Thirty-four exams. Um, that’s seventeen hours. I can probably spend a little bit less. But there’s also some overhead for getting the exams in order, writing an answer key, recording grades, and so on and so forth.
 It doesn’t help that I spent nearly ten hours on SIGCSE SV projects yesterday and today. My estimate of the total amount of time I will spend on SV activities just keeps going up and up and up.
 Sam will probably tell, too, but in a future musing.
Version 1.0 of 2018-02-13.