This post originated from an RSS feed registered with Java Buzz
by Mike Shoemaker.
Original Post: To Certify or not to Certify...
Feed Title: Unruly Rambling (java category)
Feed URL: http://www.shoesobjects.com/blog/feed.xml?flavor=rss20&category=java
Feed Description: My thoughts on software, technology, and life in general
Sometime late last summer, a coworker of mine worked together with management to facilitate Java certification's for our group. Each developer had the choice to go down the SCJP Java Programmer path, the SCEA Enterprise Architect path or to not participate. Even though I have several certifications already, I don't really find true value in them. In the past I had gotten them because the consulting company that I worked for pushed them on us. Their view was that our consultants would be more highly sought after with the certifications. I interpreted that as our billing rate's had the potential to be increased and if two contractors were even, hopefully the certification would make a difference. Regardless, I was young with lots of free time so I did them. Since I'm no longer a consultant, I wondered why I should partake in this effort. After a few days of contemplating it, I decided to take the plunge and go down the Architect route. I picked the Architect path because I think it has the biggest potential to have an upside. Since it requires the person to complete and pass three different tasks(exam, project, essay), fewer people would have it making it more valuable. My reason for doing it at all were twofold. First, nothing bad could happen by getting the certification. Secondly, heck I might even learn something.
So approximately 5 months later, I sit at St Louis Bread Company on a Saturday morning preparing for the first of the three challenges. Im finding that most of what I'm covering isn't new, hopefully this trend will not continue and I will eventually learn something useful. Anyway, back to work.
Previous Topic
