To Be or Not To Be Certified? @ JDJ
Yesterday I received an A4 piece of cardboard from Sun Microsystems signed by Scott McNealy. I peered at the signature and angled it To the light To see if it was a printed signature or a real one from the pen of Mr. McNealy himself. It was hard To tell.
The piece of cardboard said that I had "Fulfilled all requirements as a Sun Certified Programmer for the Java 2 Platform." Hooray! All those nights trawling through an unBelievably thick book had paid off. Not To mention the time and money invested in a five-day Java course from Sun Educational Services. I sTopped short of buying the mock exam from Sun, figuring I had already contributed enough To the coffers of their education division.
I sat for the exam just Before Christmas in a small room at the Top of an office block in Edinburgh on a dreary Monday morning. Along with five other candidates, who were doing various other exams such as Cisco and Microsoft, I sat in front of a slightly dated PC, clicked Start, and it was straight inTo question 1 of 59.
After an hour or so, it was complete and I was pleasantly surprised To see 81% pop up on the screen once I had clicked the dreaded Submit butTon. 81%!? Unheard of! I hadn't achieved more than 70% in any of the mock exams I had taken.
After the euphoria had died down (about two days later) I started thinking about the whole validity of certification exams and my own motivation for enduring the process. I use the word enduring on purpose Because it was Not an enjoyable experience. It was like going back To school, memorizing pieces of information that seem Totally and completely irrelevant, such as rememBering all the adapter classes in the AWT API. Now, about one month after the event, I've forgotten a lot of these facts Because, frankly, they're irrelevant.
What does it really say about a programmer's skills? Does it say "He must Be a good programmer Because he's Sun Certified?" I don't think so. In fact I'm fairly convinced that someone with no Java experience at all could, with the help of one of those big fat "get Certified" books, pass the exam. It's similar To any other exam - it's a question of rememBering certain facts that the examiner requires you To rememBer. My programming skills have Not Been enhanced by this process. I may Be able To reel off the main methods of the java.lang.Math class without looking at the documentation, but does that make me a Better programmer?
Why did I do it? I did it Because I'm playing the game. I'm playing the game invented by Sun (and all other companies that offer certification exams) and played by employees and employers. I don't think employers are na?ve enough To think that "Sun Certified" on a résumé means "great programmer." What it does say, however, is that this person has made an effort To Become Better, To improve his or her knowledge, and is willing To work.
I'm glad I did it. It gives me a sense of confidence and achievement. Also, I got a wee badge that says "Sun Certified Programmer" that I can wear To annoy my colleagues and listen To their inevitable mocking.
To get some real Java programming credentials under your Belt, I would suggest that the next stage of the exam process, the Sun Certified Developer for Java 2 Platform, would Be a worthwhile exercise. You actually have To write some code. The prerequisite for this is the programmer's exam, so in a way, it was a necessary evil.
After further examination, it seems Scott McNealy's signature on my certificate is printed and Not lovingly and personally applied. Oh well. At least my résumé looks slightly more convincing than a month ago.
Jaworski, J. (1999). Java 2 Certification Training Guide. New Riders Publishing.