As I already discussed in a recent blog entry, working with students is interesting and always full of surprises. Sometimes, I am caught in negotiations with students about the work they should do. Recently, I asked a student to write a short (eight to ten pages) report on his project to prove that he has done programming work. Basically, I was asking for a report about activities that you (should) do in a software project: requirements analysis, the motivation for the project and some technical details about the work. Nothing outrageous, I believe. However, the student started a negotiation and asked if the subversion commit log is enough proof for his work. Truth be told, first I was baffled and then amused. Apparently, when I supervise students I am the one who should do the work and the students tell me what to do:
“What can I do for you that you get the credit points for your project? Wait, let me write the report. Now, even better: let me do the actual work. Just tell me what to do and will do it. Just send me your log files and I will do the rest. Thank you Sir!”
your ikangai science team
[UPDATE]
I was contacted by the student and we had a brief EMail conversation and clarified some mutual misunderstandings. It seems, that I misinterpreted his EMail: it was not his intention that I should do his work by analyzing the log files. He meant to provide the log files in addition to his project description. This is of course perfectly ok.
With the end of contract with university in one month, I spend some time reflecting on the experiences with students that I supervised. Generally speaking, working with students can be challenging. If is difficult not to forget that students are still learning how to do things while at the same time they should be able to produce results. 