I think that the only reason to get certified in any technology is to prove to yourself that you know it. As someone who often looks at resumes and interviews people I don't think that certification will get you a job. Particularly in this job market.
That is true, a certification will not give you a job in today's market, but last year I was said by a recruiter that I should passed the Architect Certif if I want the job. Taking the Certif takes a while, and in that period of time the market can change. So if you have the Certif next year and the market is ok... The next thing is that you learn a lot by passing a certification so it worths it anyway. I would not do it for the job but for the knowledge you catch by doing it.
I just graduated and got my first programming job (which is a propriatiary language). There are few entry level programming jobs in my area and I was lucky to find one at all. I am very interested in certifications (Java and .net). Do you think that this would be beneficial for me since my experience is going to be in a language I will never use anywhere else? Thanks!
Sheri, I think these certifications would be benefitial, although I think they should not be. These days recruiters make the first pass through the resumes. They just look at the keywords and for whatever reasons some of them like certificates more than a degree in CS!!! HTH, Payam.
Originally posted by Sheri Parker: Do you think that this would be beneficial for me since my experience is going to be in a language I will never use anywhere else?
Certifications are no doubt beneficial in the beginning of a career in software development, and won't do no harm later on either. However, this certification might not be the best to start with... You should certify yourself as an architect only if you feel you're ready to do the job. Usually it takes some years of hands-on software development experience in Java and J2EE to gather the needed tacit knowledge about the tools at your exposal to be good at architecting J2EE applications. But that's just my opinion. I'd go the traditional path of programmer -> developer -> architect.
To be an Architect is about having average (good is preferable ofcourse) knowledge about *lots* of tools and technologies. So that you know how to put them together to create a solution. To be a Programmer is to have in-depth knowledge of your chosen technology area. Also, in my opinion, you need to know more than J2EE to be a Architect in real life. I can convincingly say, for example, without a knowldege of RDBMS/SQL, you can hardly architect many business application projects !
He was expelled for perverse baking experiments. This tiny ad is a model student: