|No such thing as a small change|
Re: Code Exams Revisitedby Ducati (Beadle)
|on May 29, 2001 at 23:52 UTC||Need Help??|
After going through a full year of Assembly and Java courses at University this year your post really hit home.
I think that one of the most valuable points you made is to document you code, even if it is a written exam. I can't count the number of time I have maintained good grades by doing this. It tells the marker that you might have forgot the syntax or part of the algorithm ... but you still know the theory and how you should implement it. Plus, A good prof will value this and be fair.
One piece of advice that I would like to add is to study your assignments. Your profs/teachers give you assignments so that you can put the theory into practice. You spend numerous hours, thinking, designing, re-thinking and finally coding (Actually, you should spend more time thinking and designing then coding, but that is another discussion altogether !!). So there is no better place to study from. The first thing that I do when studying for a programming exam is:
Redo all the assignments
I have found that by doing this it helps refresh your brain in a few areas:
2. Coding Style: Is it what the prof likes/wants ??
3. Types of Questions: What the prof likes or doesn't like to test and/or mark on.
4. Key Topics: What did you do the most of snd/or what was worth the most.
This has helped me to succeed thus far... I hope that it helps any of you who read this.
Good luck to all !!
"We rock the body to rock the party ... until the party rocks the body."
De La Soul