About the SCWCD

There are 11 main topics of the exam. I’d say they were all either very easy or quite difficult, there was very little middle ground in my opinion:

• Servlet Technology Model
• Structure and Deployment of Web Applications
• The Web Container Model
• Session Management
• Web Application Security
• The JavaServer Pages (JSP) Model
• Expression Language (EL)
• Standard Actions in JSP
• Tag Libraries in JSP
• Building a Custom Tag Library
• Java EE Patterns

The newest version of the exam requires 49 of 69 correct answers (70%), and touts questions that exercise your practical ability (as opposed to your memorization) more than previous versions.

How I studied

Unlike the SCJP, where I don’t think experience was of much use, I feel like my previous web programming experience helped out with several sections of the SCWCD.

I gave myself over 3 months of time to prepare for this test (as opposed to 10 days when I took the SCJP), did a lot of coding and went through most of the exercises in the SCWCD Study Guide I picked up.

I also went ahead and passed all of the relevant exams I could take on JavaBlackBelt and JavaRanch, and they helped to cover some things that the book did not.

How I’d study if I had to take it again

If I had to do it again, I’d give myself exactly one month. 3 months is too long. Even though I did a good amount of practice, I definitely forgot some of the intricate details that might have helped me on the exam. I would code, code, code just like I recommended for the SCJP. I took my own advice and I think it paid off.

I would still grab the SCWCD Study Guide as it had great examples and assignments. I found out the morning of the exam, though, that this book is for the old version of the exam and therefore the practice questions were mostly worthless. Luckily, the objectives are the same and obviously not all was lost.

Most valuable things gained

I really couldn’t care less about adding 5 letters to my resume, but some things did stick out as very positive gains because I took this exam. One of the most helpful things was learning about Listeners. I knew little about them beforehand and wasn’t very comfortable with them until I wrote a bunch of them in practice. I can think of all kinds of cool refactorings to do now :)

Another key topic that I think was helpful was Web Application Security. I already knew a decent amount about this, but the exam really helped me fill in some gaps and gave me lots of ideas to keep things secure while being simple to maintain.

I learned a lot from this experience, and that is what makes all the difference.

Least valuable things learned

As there is good, so shall there be bad. While I learned a lot about custom tags and JSP Documents, I felt like the questions surrounding those topics were just borderline trick questions. Don’t get me wrong, I did quite well on those sections, but does there really need to be questions about whether Simple Tags can nest within Classic Tags? My argument with this is that I simply do not see enough developers using that technology, especially not enough to warrant that much attention to such a small topic. The exam creators must make the exam about mainstream technologies otherwise it’s not useful.

One other nitpick I have about the exam (being a partial web dev myself), is that the sections on web forms seemed well… kludgy. I don’t remember seeing any good practical questions about web forms on the exam, the ones I did see seemed like little caveats that I knew just because I am a web dev. Do not take this exam so you can make a better website for your mom’s friend’s home business.

Conclusion

I’m very glad I took the SCWCD, and if you work on the Java EE stack at all I think it would be to your benefit to do the same. Try to get your employer to pay for it. Committing yourself to an exam gives you much more motivation to increase your skills than just studying freely. You’ll be surprised at all the things you don’t know and realize even more things that you wish you knew. I know I did.

If you are planning on taking or have taken the SCWCD, please share your thoughts for everyone’s benefit.

Related posts:

1. How not to pass the SCJP exam
2. JavaFX for the Java developer presentation
3. Javascript: Measure those “em”s for your layout

Talk to every person that is directly behind you in the queues

JavaOne is NOT just about learning, it is about networking. I challenge you to do this and I know that you will be well rewarded for it. You might even find out about good parties, more on that later. Making good connections will take your career a long way, and if you are hiring than you are bound to find people that suit just what you are looking for.

Visit at least half of the Pavilion booths

This is about learning what is out there. I have met with engineers from some of the coolest projects out there like the Large Hadron Collider at CERN. If you can get to more than DO IT because you won’t regret it.

Take sessions that are out of your league

You will really learn more if you make a point to stretch yourself in terms of thinking differently. So far I have learned a lot about emerging technologies and languages such as Scala (I learned a 10-line quicksort) and JavaFX. You will feel stupid but inspired if you do this, and you will be a more well-rounded thinker for it.

Get invited to the best parties

All this talking and visiting will hopefully score you invites to some good parties. Get to the best ones because you will meet more amazing programmers. If you are able to do only 1 thing on this list, choose this one. I know it is the most difficult one but it is the most rewarding. Tuesday night, I went to a party and met none other than James Gosling, the creator of Java!!

Go to at least 2 Hands-On Labs

Nothing solidifies your learning better than doing. So far I have learned a ton about profiling in my IDE, and soon I will write some cool JavaFX animations!

Bonus: Feed a homeless guy

I’m serious! This is nothing technical, but there are a lot of homeless in the San Francisco area. Some would argue that it encourages begging but seriously noone chooses this lifestyle. You probably make a decent salary so make someone’s day. It will make you thankful to be in the profession you are in.

EXTRA BONUS: Meetup

If you are at JavaOne than I want to meet you! Contact me and I’ll buy you a beer and share some stories.

Related posts:

1. Mindlessly easy ways try out Linux or Solaris
2. JavaFX for the Java developer presentation
3. How not to pass the SCJP exam

So just how hard is the SCJP? Instead of phrasing it in some vague way, I’m going to tell you what I did and how it all worked out for me. For starters, I studied for about 25 hours over the course of 10 days before my exam. I would say that having 18 months of Java experience did not help much. I also took 2 practice tests but they weren’t as helpful as I would’ve liked. However, I do still highly recommend reading the SCJP Study Guide by Sierra and Bates. It was fairly thorough and contained many helpful tips.

I got a depressing 55/72 or about a 76%. 59% is a passing score. From this experience I have learned these 3 important things that you might consider when preparing for the SCJP:

First, give yourself at least a month to study. Doing it all in 10 days was a mistake in that I did not really get time to assess my weak points and work on them. And I mean study at least an hour per night but don’t cram too much into the week before.

Second, write a lot of code. When I say this I mean those little programs that use some small feature of Java you don’t write everyday. Write an anonymous inner class. Use more generics. Unfortunately I was out of town without a good computer for much of my study time, and I would definitely make sure to fit this in were I to take it again.

Last but likely not least, use more than 1 resource to study. Get your materials from more than one place mainly. Take mock exams for 2 or 3 places. You might use the exams that came with your study book(s) but also consider using a community such as JavaBlackBelt or JavaRanch.

Why would one even go through all this effort for 4 letters to stick on a resume?

More than getting a certificate, I learned a ton of new quirks and small features of Java and I am now a lot more well-rounded as a Java programmer. I learned why some things are the way they are in Java which helps solidify what I already do know. Even though I mentioned that my experience did not help, I feel more comfortable using different programming structures and concepts as well as having a better view of what is possible. I can also now pursue my SCWCD certification (which I plan on having a much happier post about).

One final recommendation: get your company to pay for your certification exam. Lucky for me, mine did :) If you think that an exam is a lot at $300, compare that to the $100,000 or so your company spends on you every year (ok maybe that’s not all pay but employers pay a lot for benefits, equipment and insurance) . If it gives you even a 1% productivity increase, the returns for your company’s investment will be enormous!

Please share your SCJP experiences in the comments!

Update: Thank you to Sun Learning Services for recognizing me with an iPod Touch due to this article. Just in case you’re curious, the Sun mail did have my name wrong, it is actually me, Eric Wendelin ;)

Related posts:

1. Lessons learned from the SCWCD
2. JavaFX for the Java developer presentation
3. Continuation-passing and tail call elimination in Javascript