To Cert or not to Cert
As a software contractor, it is in my best interest to keep on my game and make myself highly marketable. You're a business, in business to sell your service, and to do so you need to be able to advertise yourself. The question is whether or not to chase certifications, such as Oracle, Java, A+, and others.
In reviewing technological certifications, they strike me as very, very poor talent and/or skill detectors. In fact, they look more like the word definition tests you would take in elementary English class. Memorize the meanings of these 10 words, some of which have value in real world language, and some of which don't, and then regurgitate them on a written exam. I'm not badmouthing English class, but to know a word is completely different than to be able to wield it. Much like these tests, they can certainly show you know a definition of a technological phrase, or perhaps a language syntax, but show absolutely nothing about your ability to use it. Using it is the real value in the software developer realm; I'd give 90% value to use understanding, 10% to definition.
In addition to questioning the value of these tests, and preparing for these tests, I also run across those who think along the lines of this. Basically, not only are they a waste, but they also can indicate you're willing to waste your time. A long list of them can also indicate pompousness. To add to this, a company that does value a long list of certifications may be populated with people who define themselves by complex syntax wielding developers, which typically leads to overly complex, hard-to-read code.
I think for now their value is questionable, and simply a way to spruce up the resume if you can't fill up the first page. Once you've got a few marketable claims, the value fades. I assume for certain companies, this may offer great value to get your foot in the door. The question is, are these the companies to work for?
In reviewing technological certifications, they strike me as very, very poor talent and/or skill detectors. In fact, they look more like the word definition tests you would take in elementary English class. Memorize the meanings of these 10 words, some of which have value in real world language, and some of which don't, and then regurgitate them on a written exam. I'm not badmouthing English class, but to know a word is completely different than to be able to wield it. Much like these tests, they can certainly show you know a definition of a technological phrase, or perhaps a language syntax, but show absolutely nothing about your ability to use it. Using it is the real value in the software developer realm; I'd give 90% value to use understanding, 10% to definition.
In addition to questioning the value of these tests, and preparing for these tests, I also run across those who think along the lines of this. Basically, not only are they a waste, but they also can indicate you're willing to waste your time. A long list of them can also indicate pompousness. To add to this, a company that does value a long list of certifications may be populated with people who define themselves by complex syntax wielding developers, which typically leads to overly complex, hard-to-read code.
I think for now their value is questionable, and simply a way to spruce up the resume if you can't fill up the first page. Once you've got a few marketable claims, the value fades. I assume for certain companies, this may offer great value to get your foot in the door. The question is, are these the companies to work for?
posted by Zach at 9:33 PM
1 Comments:
i think its better to get certified honestly (lot of certifications answers availble online) , which will keep us in the business if you have time and interest.
we cannot measure any one just on certifications . qualification and pastwork + certification will help.
yes when we are competing with all certified professionals who does not even know the basics, interview panel shoud filter them .
Post a Comment
Links to this post:
Create a Link
<< Home