Yesterday I passed the
SCJP 1.4 exam.
On my way to the
test center, it occurred to me - I might not get a good score, but the exam cannot take away all that I have learned. It�s OK whatever I get.
In the evening I went to hear a
string quartet at the university. I planned it that way. No matter how I do, I can listen to the music and forget about what happened and get my priorities and perspective realigned. So before the concert, I found my seat, sat down and opened up the program notes to read about the performers:
�The Gewandhaus-Quartett is the oldest, uninterruptedly existing string quartet in the world.� uninterruptedly. interrupted(). isInterrupted() InterruptedException. Yikes.
Java has followed me here!
As it turns out, I missed one question in the section Fundamental Classes in the java.lang package. So that comes to 98% as they say. I wonder if I should have put quotes around the composite string I had to type in.
Thank you for all the support and advice during my last anxious days before the exam. Did I make everyone else nervous too? Thank you Tom � read the question twice and answer the question.
----
I would like to express my deep and sincere gratitude to Kathy Sierra and
Paul Wheaton for this wonderful site where people of all nations and all levels of knowledge and experience can share and help each other to learn and achieve.
Thank you Dan Chisholm for your incredible mock exams. What an amazing teaching-learning tool to help us secure a deeper understanding of the concepts.
Thank you Jose Botella and Jim Yingst for generously applying your keen intelligence and expertise to help me to understand. Thank you so much for your time. It was fun.
Thank you Thomas Paul and Bert Bates for trying so hard to keep me focused. Thank you for the technical help and practical advice and your time. Thank you especially Bert for your wonderful sense of humor.
A special thanks to my two special study buddies Alton Hernandez and Andres Gonzales. I learned so much from trying to answer your questions and from your answers to my questions.
Thank you Corey McGlone, I aspire to equal your crystal clear explanations. Thank you Kathy for your many insights and extended excursions into what the exam writers were thinking.
Thank you Cay Horstmann, my first Java teacher. Thank you Arnold-Gosling-Holmes, my Java mentors, for the correct and trustworthy explanations and insights. Thank you to my father and my sister for your support.
Thank you Marcus Green & Pradeep Chopra-Whizlabs for your helpful mock exams.
And thank you to all of my victims � all who helped me by asking so many good questions. Thank you Gopal, your questions are hard.
----
I have programming experience in the procedure-oriented paradigm. As you will see, I had to start from the beginning again with OO and Java.
Java teachers:
1. Cay Horstmann, Core Java I&II, SJSU CS151 homework assignments, OO Programming &
Patterns (with Java)
2. Arnold, Gosling, Holmes, The Java Programming Language
3. Java Language Specification (& a little JVMS)
4. Doug Lea, Concurrent Programming in Java
5. Joshua Block, Effective Java
6. Andrew Tanenbaum, Modern Operating Systems (Processes and Threads)
7. Timothy Budd, An Introduction to OO Programming
8. Michael L. Scott, Programming Language Pragmatics
Exercises and mock exams:
1. Dan Chisholm�s mock exams
2. Khalid Mughal, A Programmer�s Guide to Java Certification
3. Bert Bates & Kathy Sierra, Sun Certified Programmer & Developer
4. Bill Brogden & Marcus Green, Exam Cram Java 2 Programmer
5. Marcus Green�s mock exams
6. Bill Brogden, The Collected Hardest Questions
7. Whizlabs mock exams
8. JQPlus mock exams
9. Sun ePractice exams
Other sources of help:
Practice, Practice, Practice, Code, Code, Code
Trying to answer other people�s questions
Advice from the Sun Certification Results forum
I have been looking at Dan�s questions over and over all summer and into the fall. I cut-and-paste every question into my editor, compiled and executed the code. Eventually I could predict the compiler error text or exception. I tried to answer the question without looking at the options. Then I executed the code. Anything that I was unsure of, I researched or made new examples to test. Only then, I looked at Dan�s answer and studied his remarks. Then I found the corresponding rules in the JLS. The strategy here is to be an active participant, to avoid just reading. I kept a log of wrong answers, the almost wrong answers (my choice before looking at the options) and any question that contained something I was unsure of.
I wish I had paid more attention to the mistakes I was making and to the generic feature of a question that results in an error.
I worked through the Whizlab exams twice. I began to develop some strategies, checklists and experience of what to look for. I kept a log of the ones I got wrong and ones I had trouble with.
I developed a consistent style of (theoretically) mistake-free one-pass computing, a way to keep track of intermediate results on paper, when and how to draw pictures for array access, String and StringBuffer compositions, GC analysis and
thread analysis.
In the last days before the exam, I worked the three Sun ePractice exams several times and reviewed Bert & Kathy�s exercises and exams. My guess was these two sources represent the kind of questions I would see on the exam. On the morning of the exam, I did some Sun ePractice exam thread questions for warm up.
I had a lot of trouble finishing the mock exams in time. I could either answer the questions correctly or complete the exam in two hours, but not both at the same time. On the real exam I had 12 minutes left to review. I worked straight through instead of marking the hard ones and returning to them later. I figured I would only have time to read a question once. Knowing I would only have one chance, I applied some post-exam advice given by Jeff and Colin in this forum. Look at every option and know why the one you choose is correct and why each of the others is not correct. Before leaving the question, ask yourself, are your sure, are you really sure?
I never had a chance to show that I had finally mastered my nemesis - referencing a instance member from a static context.
Here is my one contribution to the ongoing list of advice
[ November 02, 2003: Message edited by: Marlene Miller ]