I am sure discussion on whether certification is good or evil has been already in this forum so I won't start it again Instead I would like to hear your opinion on the alternative to certifications that I would like to suggest.
Namely, instead of spending time on certification you could do the following:
1) Apply to one of the Open Source Software projects 2) Contribute the best code you can 3) Create yourself a SourceKibitzer Bio with performance indicators about your contribution.
The SourceKibitzer thing sounds like a really good idea to promote yourself. One point of criticism I can come up with is that it doesn't really say anything about the quality of your contributions - just the size and the complexity (how is that measured?).
Even though SCJP does not prove that you are a really good software developer (it just shows that you know something about Java), it's still something that is well-known in the world of Java development, and many companies and software development managers perceive it as a pro if you are SCJP certified. Some of the clients I work for even require that the developers are SCJP certified.
So while SourceKibitzer sounds good, I'd not regard it as a substitute for an SCJP certificate, but rather a good additional thing to promote yourself.
Trying to avoid echoing Jesper, I guess my thought from the other side of the interview table is that certification provides a nice baseline of a known quantity (the "you must be this tall to ride" line, as it were). I see it more as educational assets than experiential. I know that someone who has passed SCBCD for Java EE 5, for instance, should know at least in theory how to write code for EJB 3. SourceKibitzer does not seem to give me that much information on the manner of contribution.
On the other hand, I think I would take SourceKibitzer or the like into account when I'm weighing experience, since it does illustrate coding experience that can be equated to job-tasks. So it's a mixed bag, not really a replacement or substitute, but certainly something I could (potentially) look at favorably on a resume.
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
posted 12 years ago
In general we track all changes done to code repository, identify authors and calculate different basic metrics for the code they have contributed. After we have measured all the changes in the project we are able to calculate the higher level performance indicators you asked about.
I won't go into the details in this forum, but if you need more clarifications I suggest to post those to SourceKibitzer Q&A section
Originally posted by Jesper Young: The SourceKibitzer thing sounds like a really good idea to promote yourself. One point of criticism I can come up with is that it doesn't really say anything about the quality of your contributions - just the size and the complexity (how is that measured?).