G
Giles Bowkett
I went and got two certifications. I'm actually planning to get a
couple more. My existing certifications are in Java, XML, and
hypnotherapy (from the most stringent hypnosis certification program
there is). The certifications I'm planning are in Final Cut Studio Pro
and Adobe After Effects. I'm going to look into getting side work on
weekends doing editing and motion graphics. A certification's less
valuable than actual work experience, but more valuable than nothing.
I think the real reason for hostility against certifications has
absolutely nothing to do with their usefulness or non-usefulness. I
think they're useful, although less authoritative than they claim to
be. I think the reason people hate certifications is that an attempt
to be authoritative implies an attempt to be an authority, and for a
big fat beauraucracy to assert authority over independent programmers
is total BS. People who think it's **offensive** BS hate
certifications. I think it's **funny** BS, so I get them anyway, every
once in a while.
There is a third group of people, who **don't** think certifications
are BS. I think those people are wrong, and if there are more of them
on this list than in the past, that's probably a consequence of Ruby
becoming more mainstream, but I still think certifications are useful,
especially if they make you study and they ask difficult questions. If
it makes you learn the language in detail, it can be good. It was over
a year after getting my XML certification that I actually used XPath
in a real-life work situation, but when that time came, I did it from
memory with no problems at all. It was all still in there.
The number one reason I liked Rails when I first saw it is because I
had looked into getting a J2EE/JSP certification. They make you learn
**all** of the JSP APIs, and it's like this archaeological dig. You go
down a layer, there's a terrible API that you wouldn't be able to use
in real life. You go down another layer, there's an even worse API
that you wouldn't be able to use in real life for the same reasons,
plus additional reasons. Then you do it all again. There's this whole
sequence of terrible APIs stacked on top of each other, where Sun came
up with something, it sucked, and then they came up with something
completely different instead, which sucked only slightly less, but
still continued supporting the earlier thing, because they couldn't
admit it sucked, and they had customers on it. And the funny part is,
you don't just have to learn all these crap APIs. You also have to
learn Sun's excuses for them. I'm serious. Those are questions on the
exam.
As long as you actually think about what you're reading, studying for
the JSP cert is an incredible education in how to **** up Web APIs
really, really badly.
(I think I'll blog this.)
--
Giles Bowkett
Blog: http://gilesbowkett.blogspot.com
Portfolio: http://www.gilesgoatboy.org
Tumblelog: http://giles.tumblr.com/
couple more. My existing certifications are in Java, XML, and
hypnotherapy (from the most stringent hypnosis certification program
there is). The certifications I'm planning are in Final Cut Studio Pro
and Adobe After Effects. I'm going to look into getting side work on
weekends doing editing and motion graphics. A certification's less
valuable than actual work experience, but more valuable than nothing.
I think the real reason for hostility against certifications has
absolutely nothing to do with their usefulness or non-usefulness. I
think they're useful, although less authoritative than they claim to
be. I think the reason people hate certifications is that an attempt
to be authoritative implies an attempt to be an authority, and for a
big fat beauraucracy to assert authority over independent programmers
is total BS. People who think it's **offensive** BS hate
certifications. I think it's **funny** BS, so I get them anyway, every
once in a while.
There is a third group of people, who **don't** think certifications
are BS. I think those people are wrong, and if there are more of them
on this list than in the past, that's probably a consequence of Ruby
becoming more mainstream, but I still think certifications are useful,
especially if they make you study and they ask difficult questions. If
it makes you learn the language in detail, it can be good. It was over
a year after getting my XML certification that I actually used XPath
in a real-life work situation, but when that time came, I did it from
memory with no problems at all. It was all still in there.
The number one reason I liked Rails when I first saw it is because I
had looked into getting a J2EE/JSP certification. They make you learn
**all** of the JSP APIs, and it's like this archaeological dig. You go
down a layer, there's a terrible API that you wouldn't be able to use
in real life. You go down another layer, there's an even worse API
that you wouldn't be able to use in real life for the same reasons,
plus additional reasons. Then you do it all again. There's this whole
sequence of terrible APIs stacked on top of each other, where Sun came
up with something, it sucked, and then they came up with something
completely different instead, which sucked only slightly less, but
still continued supporting the earlier thing, because they couldn't
admit it sucked, and they had customers on it. And the funny part is,
you don't just have to learn all these crap APIs. You also have to
learn Sun's excuses for them. I'm serious. Those are questions on the
exam.
As long as you actually think about what you're reading, studying for
the JSP cert is an incredible education in how to **** up Web APIs
really, really badly.
(I think I'll blog this.)
--
Giles Bowkett
Blog: http://gilesbowkett.blogspot.com
Portfolio: http://www.gilesgoatboy.org
Tumblelog: http://giles.tumblr.com/