IMPORTANT: The following journal is intended for the use and viewing of approved persons only and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. Any dissemination, distribution or copying of this work is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word ‘absquatulation’ has been used in its correct context somewhere other than in this warning, it does not have any legal or grammatical use and may be ignored. No animals were harmed in the creation of this journal and a minimum of Microsoft software was used. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards.
Year View| Summary| Highlights| Month View| Wednesday 1 June 2005 (Day View)
Sat 28 May | Sun 29 May | Mon 30 May | Tue 31 May | Wed 1 Jun Thu 2 Jun | Fri 3 Jun | Sat 4 Jun | Sun 5 Jun |
01.06.2005 – Wednesday 1 June – COMS4200
- • Maz, Sophie and I drove into uni, where another bad day began. I wrote test cases for CSSE3004, and then panicked on COMS4200, racing against the clock to complete everything my group members were supposed to have done but either didn’t or had done so poorly that it didn’t even work. I got an hour’s extension, but still had to submit a partially working assignment. I hate group work. I see no way to do it right except by doing the whole thing myself, and I just didn’t have the time to do that for this assignment. I am very displeased, but unfortunately too nice to mark my group members down, which doesn’t make me feel any better. I somehow feel as though it’s my fault, that I should have managed the group better; forced and encouraged them to work.
I really am not happy about the pathetic attempt they made, and the way they’ve screwed over my marks in doing so. I put in a lot of time and effort into these assignments, only to consistently be let down by my group members. One group member was supposed to spend two days testing this code, which I thought was essentially finished. I come to the code, a few hours before submission, and after it has theoretically been completed and tested, only to find that it’s incomplete and doesn’t even work. It seems that almost everything my group members wrote doesn’t work at all, and neither of them tested anything. I spent all last night writing up the protocol I designed for this assignment, assuming that my group members had written and tested their code, as they had arranged to do, and then had to spend all today interleaving my own CSSE3004 group work and fixing their omissions and errors. Now I’ll get a poor overall grade for this course, because I don’t go well in end of semester exams and the assignments, where I had a chance to make up some marks, were sabotaged by my group member’s lack of care.
I also haven’t had enough sleep for the past few weeks, and am beginning to feel rather incoherent. Fortunately, this is the last week of classes. - Night
- • To celebrate the end of an awful day, I went and saw “911 – In Plane Site”, a documentary exposé showing at the Schonell. It was quite interesting.
- Comment by Maz – Friday 3 June 2005, 2:11 AM
- I would have known some of my code didn't work if enough of the program had been finished so I could test it. Not being able to start testing after the deadline while I was working on something else.