Don't worry. I was so off my head once, that I basically missed the first few hours of the 1st year Xmas exams for the statistics part of my computer science degree. Woke up with such a hangover that went away really quite quickly when I realised what time it was. Basically ran through the main campus with a t-shirt on. In the middle of winter. Comments of "Dude, do you know you aren't wearing much clothes?", "You know it's like really cold right?", and "Do you need any help, or something hot to eat?" (bloody art students, they would soon know about living on the street with no money
) did not come welcome. Luckily my stats lecturer gave me the exam in his office. I had to use his pen and his 1960's calculator as a ruler (it had a wire to the power supply). Tops. Then went home and got very drunk again before taking the week to recover from flu. Happy days
I actually missed, hmmm, think it was 4 exams in my life. One of which wasn't my fault. The rest were totally my fault.
Best mistake I ever made in an exam was for my finals. As per usual I had squandered every opportunity to revise (when they tell you that you can't fail gives you a certain don't care factor, and the fact I *seriously* thought I was in all those college movies from the 80's) and needed some speedy revision to get the most knowledge in the minimum revision time I had left (0 days and about 3 hours total - was 1am at the time), bearing in mind I'd been to like 5% or so of all lectures for the year. A friend of mine told me about a technique he used which basically involved finding the best question (ie. most marks) from previous years and memorising it like a b**tard. Then when you get to the exam don't even look at the questions, just write it all down on a piece of paper. Voila, instant answer, and blag the rest with your natural genius. So my flat mate was on the same course and she had all the last 10 years worth of papers. Easy. So I grab them and scan through looking for an obvious question. Sure enough, some massive structure/ flow diagram effort that was supposed to explain the software development life cycle (which turned out to be only 50% correct in real life) in great and complex detail. Every year all they wanted you to do was recreate the diagram and wham, you got something like 40-50% of the exam. Tops!!!!!!! So I memorised it like a git. Which was difficult since I was a bit tipsy at the time, and was the most revision type work I'd done in a long time (tonnes of programming, just no actual study). Still, got it all done. So the next day came and true to word I take the first 45 minutes or so (of a 2 hour exam) recreating the diagram on a blank piece of paper without even looking at a question. Happy enough I open the exam and what do I see? Yep, the exact same diagram staring at me. This year the question had been changed (for the first time in a decade) to add in the complete description of each node of the diagram. F**knuts!!!!!!! Didn't revise that bit. And each node was amazingly illogical to what it actually meant. Wasn't as obvious as : Design. Could bulls*it that one, but no...... sigh.....
Cheers
I am 99% probably lying in bed right now... so don't blame me for crappy typing
