|
|
|
|
|
by corresation
4670 days ago
|
|
As someone who acquired quite a number of Microsoft certifications over the years (MCSE, MCSD, MCDBA, among others, albeit a decade ago), I'll be a voice that speaks in favor of them, and in favor of mechanisms like them. Not as a hiring tool; Not to evaluate talent; Not to prove knowledge of a domain to anyone else: For those goals they are absolutely miserable, and are why they earned such a poor reputation. Instead as a personal target for learning things that you don't necessarily have to learn otherwise, and the truth is that in this industry you can be quite successful even if you're egregiously misusing and misunderstanding the platform that you're building on. If I'm going to be doing a project in Visual Studio, or deploying a database on SQL Server, or using the security services of Windows, it is in my interest to understand the platforms that I'm using, and those certifications provided a personal goal that I could shoot for to achieve those rudiments. |
|
Exactly how I look at it. My MCSD in VB6 from 12 years ago exposed me to parts of the language I would never known existed if I didn't pursue certification. My MCSD.NET in C# did the same thing.
My MCDBA made sure I knew about SQL Server administration, query optimization, client access and every other relevant skillset with SQL Server.
If someone has a lot of experience but no certification in a particular topic it's common to bring up something they've never heard of in regard to that topic. That rarely happens with someone who is certified. They might not be an expert on it but they've at least heard of it, studied it and evaluated whether it was an appropriate tool to use for them.