Certifications
Certifications and certification work tends to be one of those button-pushing issues in the technical community. Some feel that certifications and their acronym soup are nothing more than a waste of time (and source of revenue for the companies selling them). At the other end of the spectrum, I’ve met many hiring managers and members in the Microsoft space who look down their noses at anyone calling themselves a “developer” or “technical professional” who doesn’t have a certification attached to their name or job title.
As with many things, my view of certification work tends to fall somewhere between the two extremes. Though certifications don’t guarantee that someone is exceptional in their knowledge of any particular topic, they tend to do a decent job as an indicator of one’s commitment to a technology and (in a bigger sense) their outlook on continuing education. Though I’ve been doing development work on Microsoft platforms since QuickBasic 4.5 and Visual Basic 1.0 for DOS (yes, it does exist!), I have yet to study for a certification test where I didn’t learn at least a handful of new things that proved useful in my job.
SharePoint-related:
.NET 2.0 development:
.NET 1.x development:
