11/15/2000 -- One of the great mysteries in the certification world is why developer certification has never really caught on. I have a few theories on why that may be, and I would welcome your comments as well.

If we look at Microsoft's MCSE program, there are almost 400,000 IT professionals who currently hold it, with many thousands more in the pipeline. In fact, with this many MCSEs, you could argue that the MCSE is entirely too popular.

Yet compare this number with the number of MCSDs out there (those certified as developers on the Microsoft platforms). In just the last few months, the number of current MCSDs has dropped from 30,000 to only around 10,000 now that the previous version of this program has expired. Surely this isn't representative of the number of developers on the Microsoft platform (the number of VB programmers in industry is much higher). So why aren't developers going for this certification?

Interestingly, in the Lotus Notes/Domino arena there are twice as many developer CLPs (Certified Lotus Professionals) as those holding system administration CLPs for both R4 and R5 -- a real contrast to the Microsoft programs. I can only surmise that the prevalence of these CLP developer certifications may be related to the certification requirements for becoming a Lotus Business Partner. Many of these BPs make much of their money writing and modifying custom applications for the Notes/Domino platform.

Another major developer program, Sun's Java certification, doesn't appear to release numbers, so I can't comment on its success or otherwise. But I do like the concept of the program's developer exam, which builds on the theory of the programmer exam by adding a practical assignment that must be handed in and marked.

Even with some successes, developer certifications overall tend to be less popular than their networking counterpart. In my opinion, there are two major reasons for this:

• To be a successful developer, there are a great many more professional skills required than just coding with a specific development tool. Therefore, holding a certification is not much of a guide in what the holder is able to do for clients/employers.
• Many of the later MCSEs are career-changers, who are using their certification to help them enter the IT arena. This is fine for network administrators, who can come up through the ranks with the technical knowledge from the program and learn the rest as they go. But for developers, there are many formal techniques (modelling, testing, software engineering, normalisation etc) they need to know before they can become a productive application developer. Of course, you can learn these without completing a degree, but it's an uphill task.

Even so, programmers who are cross-training from another platform to Windows have a compelling reason to get an MCSD. In this case, they already have hard-won application development experience and then can show that they have a grasp of the basic elements of Windows development. Sure, they still need some professional experience in programming these products to become a full-fledged Windows developer, but they have already proven their interest and should prove a low-risk prospect for the future.

What do you think? I'm interested in your take on developer certifications. Post your comments below. Also, in my next column, I'll be answering some of your certification questions directly. If you need certification advice, e-mail me directly at .