hit counter

I'm currently working on a DPhil in HCT at the University of Sussex. This section of the website is for an on-going 'learning diary', for me to write my thoughts and notes on various courses and my thesis.

Entries in meetings (2)



On Friday we had our school postgraduate poster presentation, which as a 2nd year PhD student I was required to participate in. I've never produced an academic poster before, let alone presented it, so I think it was a very valuable experience to have in a 'safe' environment. 

I've had a little difficulty in working out what should appear on a poster, and how much detail I ought to give. I think the conversations I had around my poster have given me a little more insight and I thought I ought to write it down.

  • Start from the research questions. I need to work out what my single over-arching research question is.
  • Present more information about the face-to-face (tabletop?) games I am investigating. It is important that there can be 15-30 participants, not the normal 5-6 that are involved in most boardgames. 
  • I need to be much clearer about my design. 2x2, draw it out. I put it in the presentation I did, so why didn't I carry that through?

I still think less text is better, so I'll have to juggle that a little, but I'm sure I included irrelevant information so we'll see. I'll try harder for my next one. (Maybe it's time to brush up on my comic-drawing?!)

I've also just had my thesis committee meeting for this year. I'm waiting for my supervisor to come back through and give me the feedback, but I enjoyed it more than last year. I got a lot of useful information on what areas I need to defend and beef up my knowledge of. Again, a lot of it centred on what I had left out. 

  • I need to introduce my topic better. Introduce Social Identity Theory properly with historical references, talk about why that not a different group theory (done very well in Jonas Heide Smith's thesis*). 
  • I need to stay focussed on my research question (write it down!). That's not just in my reading, but in my coding too. If something isn't going to have an effect on my research question, don't do it! 
  • It would be useful to think about all possible outcomes to my experiments, and what conclusions I could draw from them. 
  • I need to clarify what I'm varying, what references I have to back up why that's going to have an effect, and really look hard for 'confounding issues'. 
  • And I need a contingency plan. If my experiments take longer to organise than I'd hoped, what can I do in the meantime? How can I make sure I hit that September deadline? 
  • It might also be useful to show how I could do this using only one board game. See if it's possible. Interesting idea.

I think one of the hardest things for me to do in terms of writing is going to be including all the relevant information. I think my brevity often comes from discarding information that to me is obvious or disinteresting, and it's only when I discuss it with others that I realise I've done it. I know I do it when I'm chatting sometimes and bouncing through ideas, I hadn't realised I did it quite so much when I write. All useful feedback and a part of the learning process. 

Now. Back to my code while I wait for feedback. 


*Smith, J.H., 2006. Plans and Purposes: How Videogame Goals Shape Player Behaviour. IT University of Copenhagen. Available at: http://citeseerx.ist.psu.edu/viewdoc/summary?doi= [Accessed April 5, 2012].


Annual review

I had my first annual review last week. I feel the need to reflect on it! Review the review, as it were. 

I'm not sure if these things work the same way everywhere or even in every subject, but in Informatics at Sussex the annual review includes a student report along with a series of questionnaires for you, your supervisor and your thesis committee. The thesis committee consists of three academics, which can cause some problems for organising a date when all three are free. The questionnaires don't take too long (although I guess they could if you had enough to complain about!), but that student report was a bit of a pain. Along with the 'what have you done this year' bit, I also had to do a detailed plan of what I was intending to do next year, and a slightly less detailed plan for the year after that. And then there was the small matter of the 10,000 word research proposal and literature review. 


I know that eventually there will be a lot more than 10,000 words in my thesis. I do, really. But somehow even though I honestly did start thinking about this 10,000 words quite a long time ago they didn't really start coming together until after the whole dream abstract thing. Of course, by then I'd written 3000 words or so, most of which ended up scrapped. And there was quite a lot of panicked reading to try and fill in some gaps. But I managed to get quite a lot written and sent off to my committee even if the actual research proposal was a little like bullet points and I hadn't quite got my research aims done and possibly my 2-year plan was a bit hazy. 

Of course, what I'd forgotten was that most people haven't spent the first 6 months of their PhD coding up the framework for a game. And because that wasn't directly relevant to my research, I'd barely mentioned that in my paperwork. Fortunately two out of three of my committee members did know that. 

The meeting went ok, although apparently the third member was a bit confused about why I hadn't got my paperwork finished properly. The reading I'd done was enough, I could answer a lot of the questions put to me (although new areas were mentioned). They thought my question/research area was interesting and had a lot of potential. But there were one or two things I've learned that I wanted to note down: 

  1. I got really quite stressed in the end about this. I need to not do that. I think part of the problem was not really knowing if what I was producing was right (as in what I was supposed to be producing, not as in factually correct) or enough, so next time I need to get a little more of my supervisor's time (further out) and make sure I have something she can read well in advance. I checked my style with her, next time I need to check the content too. 
  2. When there's two things listed on the requirements (research proposal AND literature review) I must not get totally fixated on one (the literature review). Yeah, yeah, easy to say. 
  3. I need to put together a document template INCLUDING PAGENUMBERS! And use it for all of my documents. I thought I had, but I forgot the page numbers. 
  4. When asked what I've done over the last year (which is actually only 9 months anyway), I mustn't ignore 6 months of work. I should have worked it into that report and make damned sure it was clear I hadn't just been twiddling my thumbs.

I think it's been really useful for focussing my mind on the PhD/research side of the project. I really do feel like I have a better grasp on what I'm attempting. Hopefully from here on I can do a better job of balancing the programming and the research thanks to that. 

And they let me stay for the second year! Woohoo!