Got my SCJP... share your pass/fail experiences here
Hi all,
I just passed the SCJP exam. For understanding, I followed the Sun's Java tutorials; and for cramming, Paul Sanghera's book. I've extensive background in C/C++ but I've only written toy programs in Java.
The exam was ... interesting. A mix of questions, all related only to language features mentioned on Sun's certification website, almost no real-world examples (except the has-a vs is-a questions). In language Qs (95% of exam :-)) some tested fundamental understanding of OOP, control etc (e.g. what it means to have "A implements I; B extends A", or case without break), some that tested Java-specific features (e.g. anonymous classes, auto-boxing/unboxing) and some that apparently tested how much rote memory you have about Java classes (e.g. what methods Locale offers). Personally, I found the last type a bit offensive (maybe I am just old and crotchety). I know how to reference Java documentation online, why do I need to memorize the stupid method names?
What were your experiences?
Hm, it's ben a while since I passed my SCJP, so I don't really recall the details....
I would have agreed with you heartily, Naren123, a few months back...but lately, I've realized that it does help, albeit, maybe, in some obscure, unapparent way, to memorize the method names. Because you may not always have documentation handy. I hate memorizing such stuff myself. I think it's a waste of brain-power that could well be utilized in remembering important stuff, like the fact that the answer to life, the universe and everything is 42 :). I'd much rather learn these things through practice; use the methods in some applications. Preferably repeatedly so that it is drilled into my head.
But the sad fact is, you will be required to. Sooner or later you will need to recall the method, maybe for some job interview or perhaps at a brainstroming session for that new module. It would definitely help if you said, 'Right. So we can use .makeMyJobEasier() here and make our job easier' rather than 'Umm. I'll have to look up the documentation and check, but I have a vague idea that there is a .doTheSameThingInALessEfficientAndRoundAboutManner() here that just might mess up the code in our effort not to learn up methods' :)
