It's official |
But the main reason I decided to keep at it is that certifications focus your studies. It's easy to read random programming books on a lot of different subjects, but you're not likely to retain the knowledge if you don't have to prove it in some way. This is the whole reason college was invented. One way of proving yourself after college is through side projects. Another is certification. Of course, whatever you can do to stretch yourself beyond your comfort zone is a good thing. I do this in a variety of ways, one of which is certification. (This blog is another!)
Another kind of certification
Some people scoff at certifications, and they're not always worth the effort. Make sure that a test will actually be relevant to your work, or at least the work you hope to get. Even though I code a lot in ASP.NET, the .NET Web Applications Development exam was not very useful, since I don't do much JQuery or MVC. It was hard to practice the materials, and I doubt I've retained much knowledge. Make sure you understand what skills are being tested.
One shouldn't forget the cost either. None of the tests have been easy, and failing them can be pretty costly, in terms of both time and money. I know plenty of very smart people who just aren't great test-takers. The whole process can be very frustrating, starting with figuring out what test you should actually take. But it should get easier after your first one.
Are there any other pro's or con's I missed?
No comments:
Post a Comment