Java Certifications from Oracle (Sun)?

Question

Java

In a week I will take the SCJP and I want to outline my plans for the future.
I really liked the article on Habré on this topic - habrahabr.ru/blogs/java/84405/ which describes the experience of passing SCBCD.
I'd like to hear some feedback on the experience of taking these certification exams:
- Sun Certified Java Developer (SCJD)
- Sun Certified Web Component Developer (SCWCD)
​​- Sun Certified Developer For Java Web Services (SCDJWS)
Thank you in advance for your answers.

Answer 1

The question becomes even more relevant, as the SCJP has already been successfully passed.
So far, I’m mostly looking towards SCJD…

Answer 2

Passed SCJP, SCJD. The book “SCJD Exam with J2SE 5
” by Andrew Monkhouse and Terry Camerlengo helped me a lot to prepare for the exam. It discusses such an application, provides information about preparing for the written exam, and the assessment process by the examiners. The Coderanch forum was also very helpful: www.coderanch.com/forums/f-25/java-developer-SCJD .
With motivation, everything is right - along the way I mastered many things in Java - working with files, RMI, sockets, Swing, multithreading, Java Doc. A good line in the resume, after the addition of which the response to my resume increased significantly. True, when interviewing for a job (I'm talking about states) it didn't help: few people pay attention to these certificates and ask all the same basic questions again. There were even those who asked what kind of certificates they were. Also now SCEA cannot be passed without a second level, so this is a sure way to pass this exam.
However, there are also disadvantages. For example, Swing is already very outdated and stopped being updated a long time ago. The library itself is not written very nicely. But as an introduction, it's fine.
I worked on the project for half a year, on weekends, slowly. I recommend doing the project in several iterations. First, throw in the main functionality, then refine, refactor, polish. Write documentation along the way in general terms so that you don’t have to write it at the end. Write tests, then functional. Those. use the practice of modern programming - it's much easier to manage the project. And do not forget to constantly peep into the main task - there are many nuances, the failure of which can lead to failure of the project.
In general, I recommend :)
For motivation: picasaweb.google.com/lh/photo/MMWtQFfTx2kV5yf90aX1DQ?feat=directlink