This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Congrats vladimir Thanks for the tips. Did you got any question on painting ? is painting in the objectives ?
Joined: Dec 19, 2000
I don't think there were many questions relating to painting on the exam. Painting/Layout Management/Event Handling were definitely some of my weaker points when I was studying for this test as I have been doing mainly Web-related work with Java professionally. I would say that the level of coverage in Simon Roberts' book on these topics is good, and he makes it clear which things are part of the objectives and which aren't. My philosophy was that since I was weak in these areas, I could use the exam as an excuse to learn more about them, so among other things, I wrote a simple little paint program using just AWT (I didn't want to confuse myself by using Swing). Many people on this forum seem to take it as their goal to pass the exam, and they want to do the minimum amount of work to pass. I think a better approach would be to use the exam as a form of motivation to improve one's basic knowledge of Java and to do some more practice programming. Frankly, while I think Sun's programmer exam is good as far as it goes, it really does not do much to prove that someone is a good or qualified developer. I would not personally consider it useful for anything more than the hiring of a junior-level developer.
You did so well on the thread. how did you prepare it and what book did you use? I have a problem with the thread. Could you please send me your advice on thread to email address: email@example.com. thank you, Jimmy
hey.. congrats .. that's a very good score .. i feel that we are all concentrating a lot hard on the certification part of JAVA, basic the industry demands that we need to be certified ..actually even after clearing the certification, i personally feel that there is a lot to be desired .. i have a couple of friends how have cleared the certification and they are finding it very difficult to come in terms with the industry standards .. it is no doubt true that if u read the chapters from the certification book like complete certification from roberts, u may pass the exam.. but really it is not enough ... anyway.. i would like to recommend a book for all people how seriously want to learn JAVA programming apart from just the certification : JAVA - HOW TO PROGRAM (THIRD EDITION) BY DEITEL & Associates Inc. congrats and all the best .. bye
Hello Congratulations!! its really a great score and i just saw ur score,i was surprised to see that u have scored 100% in threads as i have seen people saying that threads are very tough.I think ur the person who can help me out.I am writing the exam very shortly,so tell me what material did u refer for threads and how should i go about threads i have only 12 days in my hands,if u have anything to say more on the exam please mail me and my mail id is firstname.lastname@example.org and if u have the material for threads pls send it to me. thanking u in advance vasanthi
hi ! Congratulation for the excellent scores you got...
I am planning to appear exam in the second week of January. Means only few days left for me. If you can give me last minute tips then i will feel free. Hope that u will share ur last minute experiences and study pattern..
Joined: Dec 19, 2000
Re: vasu matt, posted December 25, 2000 09:48 PM
As I've pointed out in the document that I've put up on my Web page, the two books I read to prepare for the exam specifically were the ones by Simon Roberts et al, and Bill Brogdan. They do a good job of covering threads as far as I am concerned.
For various reasons, threading is a somewhat intimidating area to study. I think the most important thing to understand is that the purpose of threading is pretty simple: To allow a single program to do more than one thing at once. Writing multi-threaded code is an excellent way to prepare.
In addition to the fundamentals of creating new threads, getting them running using the start() method, etc. Understand how:
threads can become deadlocked when two threads are waiting for each other to release needed resources (eg. thread A needs thread B to complete at the same time that thread B needs thread A to complete)
data corruption can occur when multiple threads are accessing the same shared data simultaneously
synchronized code blocks together with the wait() and notify/notifyAll() are used to prevent data corruption due to this simultaneous access (and again how one must be careful to prevent deadlock as Java does not do any checking for it on its own).
What else can I say? I am not going to go into detail about the exact types of questions I got about threads on the exam, and I don't really remember them anymore anyway, but if you understand the concepts above, then I have a hard time imagining you would fail the threading portion of the test. I was about to take the test when I got cold feet and postponed it for a week. You can re-schedule your test as late as the working day before you are supposed to take it, so if you don't feel ready, put it off and keep studying. If you have specific questions about threads, I am sure they can be addressed in this forum or others like it.
Re: manish parnerkar posted December 26, 2000 12:55 I really wanted to feel ready for this test. I spent a lot of time preparing for it. I was nervous, and I didn't want to fail it on my first try. My friends kept asking me how my studying was going, and I was pretty scared about facing my co-workers and saying I had failed it. The week before the test I wrote quite a lot of sample code to really nail things down in my own mind. I concentrated a lot on understanding the details of inner-classes, which was a good thing because being confused about innner classes would have hurt me on the exam; they seemed to appear in almost every question, even the ones that were not specifically about how inner classes worked. In addition to inner classes, I did a lot of work with the threads and awt/painting/awt events/layout managers. These are topics I was weak on and really tried to get a good handle on. My weakest topics was IO, as reflected in the final results, because it seemed like a waste of time to me to worry about the details of java IO. Finally, the weekend before the test, I spent three hours each day re-doing some mock exams for the second time. I did three in total (Simon Roberts + 1 of Bill Brogdan's + 1 Marcus Greene). I also did Brogdan's 19 hardest the Friday before my exam (I took the exam on Monday) and got only a few questions wrong on it. I found it very hard to get into the exam, and left the first few questions blank as they seemed to be written in a foeign language. Eventually I settled down and I guess I did OK on the test. I thought my final score was pretty good, and I was rather surprised to have done so well. Even though I may have over studied, I think the approach I took is a good one, and I learned a fair bit of extra stuff that wasn't on the exam as part of my study process, which is a good thing. Vlad