Saturday, 21 November 2015

GTD Made Simple: Why I think the Internet needs one more blog post about "Getting Things Done"

I'm naturally disorganised, but I have so much stuff to do that out of necessity I get organized. (Then more stuff comes and I get disorganised again.) The way I get organized is by attempting to follow a system called GTD. GTD comes from a book by David Allen called Getting Things Done. The book is an unusual read, a mix of management-speak, Zen-speak, and tips for organizing your filing cabinet. But for all that, it's a good book.

GTD has become popular with many different types of people. It is especially popular with tech people on the Internet. It's a bit of a geek cult, which is strange. Why are computer programmers singing praises for a management consultant? Indeed, why are university professors?

Lots of people on the Internet have been writing about GTD. It can be hard to get started. For one, the book itself, the writing isn't always succinct. Also, cleaning up your to do list and blogging about it is a good way to procrastinate. So, there are lots of blog posts out there about GTD. Lots.

I have been trying to figure out a way to explain GTD that makes clear how simple it is.

Look, you need a to do list. It will clear your head so that you can concentrate on your work. That's it. That's GTD.

But you've tried this already. It helped for a little bit, but then it stopped helping. This is where GTD gets interesting. It's based on an extraordinarily perceptive understanding of why to do lists stop working. They can stop working because:

  1. You haven't written everything down. To do lists become way better when they contain literally everything that you have to do in life. If they don't, then deep down in your mind, you will always know that you've got stuff to do that isn't written down, so you spend mental focus trying to remember those things. It's like if you tried to keep a calendar but only wrote down half of your appointments in it.
  2. Your list is too vague. If you write down something like "Dentist" on your to do list, every time you see it, you need a little mental energy to work out what that meant and plan what you need to do about it. But after you've done that planning, you don't do anything about it, because you were just scanning your to do list and right now you need to do something else instead. This makes you anxious. And if you read "Dentist" without taking that effort, then you still feel anxious because it reminds you that there's something you need to do and you're not sure what it is.
  3. Your list is too long. When you're not sure what to do, you need to be able to scan your list quickly to decide what to do next.
  4. You can't find items right when you need them. If you're about to drive past the hardware store, you need to be able to stop in the parking lot and quickly find the list of stuff that you'd been meaning to buy.
  5. You can't write down items right when you think of them. When you notice you're running low on toilet paper, you're not usually in the grocery store at the time. But you still want to record this right then, so you don't have to remember it until you're walking past the shop the next day.
  6. Your list doesn't keep up with your life. Gradually you get more and more things to do that just don't make it on to your list.
  7. You don't compare your list to your bigger goals. Urgent things aren't always important, and it's easy to let days slip by you. You need to think about what's most important in your career and your life, and your to do list needs to contain actions that help make the important things happen.

GTD is a system for keeping lists that is designed to avoid these problems. GTD doesn't care where you keep your lists or how you store them --- this is why geeks love GTD, so that they can keep arguing about what software is best. But you don't need software. Paper works fine. What you need are principles to guide you.

The main principles of GTD are:

  • Record everything. Everything that you need to do.
  • Record everywhere. No matter where you are, you need a way to write things down so that they will end up on your list.
  • Organize by context. You want multiple to do lists, organized so that when you scan a list, it contains only things that you could do right then, if you decided to. You might have a list of people you need to call, a list of things to do at a computer, a list of things to do at home, etc.
  • Specific measurable actions. This the caveat to "record everything". If it goes on your list, it needs to be something specific, that you could do right away, finish, and tick off. Instead of writing "Dentist", you should write, "Email Morag to ask for dentist recommendations". When you read an item on your list, you don't want to think "Oh, what was that?" --- you want to think "Ah, I can do that!"
  • Small specific projects. A project is anything that takes multiple specific actions to accomplish, even if it's only 2 or 3.
  • Plan naturally. For any project, work out what you need to do on the sheet of paper, and add to your list the actions that you can do right away. Actions that you need to do later down the line, they don't go on your list.
  • Review weekly. Check your calendar and your notes to see if there's anything that you need to do that you haven't written down yet. Think about your longer term projects and goals and make sure your lists have actions that help with them.

How you organise a set of lists, and supporting files, to meet these principles, that's what the book is about. It may not always seem so from the surface, but the book is full of clever little tricks. That's another reason why the book can be deceptive: It's easy to admire the tricks but not understand the system. But if you really understand the principles, then the practice becomes much more clear.

Sunday, 27 September 2015

Why you should scrunch your face when you think

An important skill in any type of creative work is to observe and reflect on your own habits of thought and discover a way of working that suits them. A simple example is the old advice to notice the time of day when you have the most energy, and reserve that time for the most creative aspects of your work. But there are many more examples of this, if you look for them. It helps to be a bit self absorbed.

One habit that I've just recently reflected on is that sometimes I close my eyes and scrunch my face into an "I'm thinking hard" face when I'm trying to think hard. In some sense this is an affectation. But I like to think that the goal is more noble, to harness the cognitive dissonance that would result if I make the scrunchy face without thinking hard. To escape this dissonance, the only option for my subconscious is to actually start thinking hard. It feels like this helps, at least sometimes, but I haven't kept careful records. And at least everyone else can see how hard I'm thinking.

Thursday, 28 May 2015

My Top Conference Attendance Tip

One of my PhD students is on his way to his first academic conference. Conferences are one of my favourite parts of research: I've met so many interesting people and started so many fun collaborations that way.

Just today I saw this great advice from Michael Ernst about attending conferences. His advice is so good, that I've only got one thing to add.

Here's my tip. When a big group students from the same institution go to the same conference, they'll often hang out together all the time: at meals, coffee breaks, etc. This isn't a great strategy on their part, but you can exploit this. Once you make friends with one person in the group, now you can go with your new friend to lunch with everyone else in the group. Voila, now you have a network!

This is a general principle of networking (horrible name, but incredibly important if done honestly and well): Cool people will help you to meet other cool people. And once you've been around long enough, you can return the favour!

Saturday, 11 April 2015

Viva la voce

One of my favourite aspects of academia in the UK is the final oral examination for the PhD --- formally called a viva voce, which everyone seems to call a viva (VEYE-vah). The viva is an oral examination that typically consists of the student and two examiners, one from within the University (the internal examiner), and one from outwith the university (the external examiner).

Both examiners read the thesis carefully, and ask the student detailed questions. The traditional way to do this is that all three have a paper copy of the thesis, and the examiners go through the thesis page by page with their questions. Some questions are high level ("Why did you choose technique X rather than technique Y?") and some can be very detailed ("In your proof of Theorem 4.3 on page 176, I'm not sure that the third step is correct. What if the matrix A is non-singular?").

This discussion commonly takes 2-3 hours. Longer and shorter vivas are not unheard of, though if you ask me, a one-hour viva is a bit of a rip-off for the student, and a five-hour viva isn't kind, unless the length is caused by the student being exceptionally argumentative or loquacious.

At the end of the viva, the student is asked to wait outside, and the examiners decide whether the student should be awarded a PhD, and if so what corrections to the thesis are required. The most common outcome is a pass subject to minor corrections, which the student is allowed a few months to complete.

Essentially, in my experience a viva is a detailed technical discussion of the content of the thesis. Most students start out nervous, sometimes exceedingly so, but relax after a few questions as they realize that this is just a technical discussion of the sort that they have had many times before. That said, even if your research career is long, it is rare that a trusted colleague will provide you with several hours of detailed feedback on your work. To be part of a discussion like this, on either side of the table, is a privilege: most work is ignored, so any criticism is a compliment.

I am sure that the process is more tense if the examiners believe that the quality of the thesis is borderline --- fortunately, I haven't yet been asked to examine a thesis like that. If portions of your thesis have already been published in prestigious venues, and whether this is possible at all varies greatly across disciplines, then you can be fairly sure that your thesis is not near the borderline.

A colleague suggested to me once that a viva is like a negotiation. If your thesis represents a sufficient amount of research of acceptable quality (and if it was indeed you that wrote it), then you will pass. The negotiation is over which corrections will be required. Responsible examiners do not want to require additional experiments that will require months of work, if the thesis as submitted is of excellent quality. But they also don't want a thesis to be passed with gaping holes in its argumentation. The purpose of the discussion is to sort out which potential concerns are which, and your voice in this discussion matters --- you wrote the thesis, so you are the expert in the room.

Sometimes an examiner asks a question with an eye to a correction being required. Maybe you think, "yeah, that's a good point, I should add a paragraph on that" --- in this case, don't hesitate to say so. On the other hand, if providing a good answer to the examiner's question would require months of additional research, politely explain why, while also giving the best answer you can given what you do know. What you don't want to do is argue every point strongly, even when the examiners are clearly right... that is not good negotiation strategy.

A bit more about who attends the viva. The internal examiner is not the supervisor, in fact, they will not have been involved with the thesis research at all. It is not unusual for the internal examiner to be a bit of generalist with respect to the thesis topic, although when I have served as internal, I have usually been able to make out the thesis reasonably well. Presumably this is because the School of Informatics is large enough that there are many theses in machine learning and natural language processing that need to be examined.

The external examiner is chosen specifically for their expertise in the subject matter, and to serve as an external is generally seen as a minor indicator of prestige. A certain amount of deference is paid to the external in the culture of the process. Even so, I have the sense that part of the role of the internal is to be accountable to the University (for following correct procedures) and to the student and the supervisor (to make sure that the examination is fair to the student). I have read and heard horror stories of aggressive external examiners but never witnessed one; to the contrary, the examiners who I have witnessed have all gone out of their way to be kind to the student.

The role of the supervisor in the viva, I think that this may vary slightly across institutions. At Edinburgh, the supervisor is allowed to attend the viva, if the student permits, but not to participate in any way. In my experience as internal examiner, the supervisor has attended about half the time. One supervisor silently took notes to share with the student, which I think is quite a kind thing to do.

Finally, although the description is written for a US audience, British academia also fetaures the snake fight portion of your viva.

(Written in honour of my first PhD student graduating. Congratulations Yichuan!)

Saturday, 3 January 2015

Early to rise, early to read research papers

Due to a recent bout of jet lag,1 I have found myself this week waking up at 5am.
So I am experimenting with reading a paper first thing in the morning.

I am hoping that starting off the day with an intellectual task will help me to avoid
"administrator brain", which FSP describes in an excellent post.

So far (well, two days in) it has been really fun. It helps me to stay motivated, because after writing 50 emails in a day, your mind gets lost in minutiae, and you forget that you came to this job to learn, to help people, and to be creative.

Can't promise that I'll keep waking up at 5am, though.

  1. I have begin scheduling posts well in advance, so this bout will no longer be recent when you read this. 

Saturday, 6 December 2014

Taste in research, and the paradox of deciding what not to work on

A large part of taste in research is deciding what not to work on. You might choose not to apply method X, even though you don't really understand it, because it has a reputation for being fiddly and difficult to get right. You might choose not to work on topic Y because you think that even though there's a lot of people writing papers about it, its goals are too ambitious to ever be met. This extends all the way to entire fields of research. I could name a few popular fields within computer science — with active research communities, large amounts of external research funding, leading researchers with fancy prestigious awards — that I suspect are being investigated in entirely the wrong way, and that I personally think are currently pointless.

I could name them. Will I? No.

Why not? To protect my career? If I am honest, probably in part yes. But what I tell myself is different. The real answer, I think, is that my opinion of these areas is poorly informed. Because I think these areas are uninteresting, I haven't studied them carefully, and so I don't know how they've attempted to address my naive objections. It would be arrogant and professionally irresponsible to publicly denigrate the hard work of many people without having even bothered to read it.

This leads to a paradox. It's impossible by definition for me to become better informed about these areas, unless I decide to actually start researching them. In order to be fully confident that an area is uninteresting, you need to study it — and that study itself is part of doing research! But you can't do careful reading on every research area that seems bogus at first impression, because then you would do nothing else. Instead, you have to take intellectual shortcuts, and do the best you can with limited time to think. Those research areas that smell a bit off, you ignore them until either they die out, or a major success forces you to reevaluate. Part of taste in research is deciding what to study, and what to ignore.

This is the paradox of taste in research. Your decision of what not to work on is, by definition, always ill-informed.

Wednesday, 5 November 2014

Mnemonic poetry and Guy Fawkes night

I walked home past several people setting off sparklers and fireworks in the meadows. In Edinburgh celebrations of Guy Fawkes night are not elaborate, but you can smell the gunpowder.

A good thing, because otherwise I can never remember what night it is. The traditional rhyme

     Remember, remember, the fifth of November

is about the worst possible mnemonic that I could think of. It fits the meter just as well to say

     Remember, remember, the FOURTH of November

but you aren't meant to remember that one. Personally I prefer

     Remember, remember, the ninth of November,

because that happens also to be my birthday.

Much more sensible to base the rhyme on the part that's easiest to confuse.
Instead, how about:

Let the memory survive
      That the king was still alive
          On November five.

Now you won't forget.