Fellow ranchers, As C-Day(Certification Day) approaches I'm just trying to make sure I avoid all of the pitfalls of dumb mistakes on the exam. I've noticed on some of the mock exams I'll make between 3-6 dumb mistakes. Which could make the difference between being a SCJP or a sad attempted SCJP. I define dumb mistakes as errors that are made even though you know the correct answer but are done in haste. So does anyone have any advice? Also I've noticed that I seen to do better with code based questions as opposed to theorical. Has anyone else noticed this? Any advice to help me contain my nerviousness? Regards, Travis M. Gibson (Future SCJP - Nov. 19, 2000)
Regards,<BR>Travis M. Gibson, SCJP<BR>Java Developer<BR>www.travismgibson.com<BR>email@example.com
Joined: Nov 14, 2000
TAKE A DEEP BREATH - before answering a/next question. Don't attempt to hurry, read the question carefully, check what they are trying to get at, evaluate all the given answers even if the 1st answeer seems to be right don't rush, be conscious of the adrenaline is pumped into your system during the exam, try relax remember that this is not a race, keep track of your time, there should be ample time as I have never heard that anyone ran out of time. Remember to TAKE A DEEP BREATH between questions and Finally the quote "HASTE IS WASTE"
Joined: Sep 23, 2000
What a nice advice there. Well even I am concerned about that. I am just hoping that the questions will be clear about their objectives and not tricky. Although I am not too concerned about few marks here there, that is a part of life.
Joined: Oct 06, 2000
I couldn't agree more- I've been writing mock exams and have been experiencing the same thing. Just really ridiculous mistakes (sometimes selecting things that work when it asks for things that don't work). So I decided to stop looking at which question I'm on and also how much time is left and easily improved my avg score about 10% just by slowing down and absorbing the question before doing it. The best part is, I noticed the overall time is maybe only 10 or 15 mins longer than "rushing".
Joined: Aug 24, 2000
Vijay is right there. If you don't understand the question upon reading it once, READ IT AGAIN. In order to read the questions completely and comfortably, you will need to know where you stand vis-a-vis the alloted time. Remember that to solve 20 questions you get 30 minutes(60 questions in 90 minutes). Keep a track of this as you are giving the exam, every 30 minutes. Do not try to track the time for every question, as the time taken to solve long code related questions may be actually 2 1/2 minutes, but the time taken for a simple and short objective question may only be 1/2 minute. All the Best. Richard Miranda.
Shubhangi A. Patkar
Joined: Sep 20, 2000
Hi All... What a relief to find out that I am not the only one who keeps doing this Only notes that I did to myself afterseeing theresults on few of my first mocks was "pay attn to qtn.u dumb gal!" Overconfidence? may be. Needless hurry? definately. Trying to kkep track of mocks the way maha anna suggested is a really good way of preparing yourself. All the best to you Travis Shubhangi.
Originally posted by Donovan Yung: I couldn't agree more- I've been writing mock exams and have been experiencing the same thing. Just really ridiculous mistakes (sometimes selecting things that work when it asks for things that don't work). So I decided to stop looking at which question I'm on and also how much time is left and easily improved my avg score about 10% just by slowing down and absorbing the question before doing it. The best part is, I noticed the overall time is maybe only 10 or 15 mins longer than "rushing".
[This message has been edited by Shubhangi A. Patkar (edited November 18, 2000).]