if I am a Koala which
This is what I did last week
Monday: I woke up at 5 am. I did not sleep Sunday night. Ever since the semester got over and I had no 9 am classes to attend, I have kept pushing back the time I hit bed in the night, often reading up late, or watching a movie, or spoiling another persons schedule by chatting up late.
I also had a trivial matter of finishing up some examples that I was making for my adviser’s book. 2 among them were exceptionally straightforward, and I had been avoiding typing it up. And, I did those two problems in 2 hours of non-stop work on Monday morning, from 6 to 8 and then slept off. The whole afternoon went in a meeting with the adviser to get the examples fixed in his book, and I saw a movie in the evening and dozed off
Tuesday: I hoped that a Monday with as little sleep as possible would get me back to normal schedule. And it almost worked. Went to office by 10 and started working on the last example that I had to finish. It was for a chapter that is not directly related to my research and I had to use another student’s code, and I spent a lot of time trying to figure out if bugs in his code were not actually bugs. Late morning was another short meeting with the adviser, and then I slacked off for most of Tuesday, doing nothing, (except getting frustrated at apt-get upgrade and even more frustrated with installing Octave 3.2.0)
Wednesday: Wednesday was the day for the scheduled bi-weekly research meetings with the adviser. I woke up at 9, but lazed around in bed till noon, made lunch and strolled into office at 1:30. Played around with the last example, and convinced myself that there were bugs in the other students code, and went into the meeting with no progress to show, but a question that had bothered me for 10 minutes a few days ago regarding the model that I was using. Luckily, that question was enough fodder and we spoke for an hour about it. It has become a norm that I hardly work after research meetings, and I came back home and slept.
Thursday: Was less lazier than Friday. I spoke to the other student for about 15 minutes. He understood his mistakes and said that he will finish the example. So, one work less for me. I came back and spent time making my system work like before after installing Octave3.2.0. Downloaded a few papers, which I thought would give me some super idea to further the ideas that the meeting on Wednesday generated. Read a few of them, and each one of them was crappy. Thought a little, and got an idea anyway. All this took around 45 minutes. The “intellectual” strain made me tired and I slept off, woke up later and wrote the previous blog and then dozed off again
Friday: Was the laziest of all. Woke up at 9, but decided that I need to finish the awesome dream that I was having, and so slept and tried to recreate the awesome settings of the dream. But, what is awesome when you are in deep sleep, is plain illogical when you are semi-awake and try to recreate it, but free association in a semi-awake state can lead to colourful dreams, and I dozed till 3 in the afternoon, made lunch, had it, and napped again till 6 (this was because of “An Equal Music”). Rishi called at 6, and spent the next six hours drinking beer (Self note: I am getting older, and my body rebelled for 3 22 ounce glasses of beer with vomit last night. Need to decrease the amount to just 1 beer) and chatting aimleslly.
And finally on Saturday, I analyzed the previous week and realized that I spent 7 hours meeting my adviser, 2.5 hours working on the examples, 1 hour downloading and reading paper, and generating an idea (which in all probability will be thrashed next meeting), and slept for a massive 58 hours the previous week, averaging nearly 12 hours a day. The question that begs to be asked is:
Am I so lazy because the PhD affords me the luxury of being lazy (ya! most of the time no boss and no deadlines) or is it because I am so lazy that I opted for a PhD?
So, I have made myself this plan, to finish work that in my lazy schedule, I would have taken ages to do, but in actually, would not have required so much time, and a little ambitiously, plan to finish it in 10 days. I have a feeling I won’t be, but I am sure I will do a lot, if I actually get to office and work furiously. Lets see
PS: The first “no” in the last column needs to be taken with a pinch of salt. I prepared this to-do list almost at the verge of being bored with work. I decided not to split the work in item (1) because then there is a flow to the to-do list. But let me see how subsequent updates on the plan works!
Sunday: Another “no”. I realized that making the matrices was not as trivial as I thought it would be. But, it is boring work, because the fun begins after the matrices are coded up. Also, a plan to go to Chicago might just materialize next weekend, so a major blow to my plans. Lets see what Monday brings!
Monday: Work was progressing smoothly, till my computer decided that it has been used enough for the day and refused to work. Don’t know how much of a setback this is going to be. Hopefully, it can be fixed easily tomorrow.
Thursday: Way Way behind schedule. By the way of explanation: 1. The work is way too boring. I have to carefully type the code, but do not have to think. It is just a matter of writing up around 300 lines of error-free stuff. Just too boring. 2. Adviser is not in town next week, so the next meeting is well into the middle of July. Hopefully, I can finish stuff by then. 3. German class is at 9 in the morning. My schedule is all affected because of waking up at 7:30.
Friday: Back to scratch now. Realized that the code that I am writing is getting clumsier and clumsier as I move to steps 3 and 4. Need to redesign 1 & 2 to make 4-10 easier.