There is no question that being certified in something, is a good thing. The badge that says ?you are capable? at dealing with a specific technology or performing a certain task. Some of these are rather large and I don't mean to downplay them at all. However, it's been my experience that certification can sometimes be used as a cruch. The money making schemes of those issuing the certification or in some cases, a corporate marketing ploy to advance product recognition.
My understanding isthat certification programs manifested as a result of vague CS degrees from Universities and the rapid emergence of new technologies, protocols, and methodologies. To be certified meant that you could ?handle? the technology, but so does proven experience. Think of the web developer; graphics, special relationship, scripting, human factors, and a bit of networking thrown into the soup. These people would need to spend most of their earnings on certification, in order to ?prove? that they canbuild a multi-tiered web structure. In actuality, most of them merely build a bigger mouse trap, I mean website.
But I digress. If you are going to work with a specific technology, say Solaris, and that?s going to be the main part of your world, then you should get certification, not for prove that you understand what you?re doing, put to make certain that you know what you know. If on the other hand, you?re going to be certified in something like a methodology ? then it?s more of a culture(corporate and other) concept and you could more effectively ?show? your working knowledge of it.
Ah, I think that?s what I think; certification in a point of technology or an aspect is a good thing, experience shows that you understand how the wave of technology is flowing.
Personally, most of the certifications that I see are in the hands of people that don?t really show me that they can handle it.
-an opinion