On the value and meaning of IT certifications.
I love certifying and have earned 25+ Technical certifications in my field. In this article, I'm going to explore misconceptions about certifications, the meaning of certifications, and share my own method of self study.
Misconceptions and meaning:
Comments I've heard over the years:
What certifications actually do:
What certifications do not do:
The eternal tension between theory and practice:
Those who prefer to "learn on the job", can fall into the trap of only learning what they need to, in order to solve the problems they come across, or what interests them personally.
But there's a certain tunnel-vision to such an approach - Environments tend to experience a narrow range of similar problems.
A certification, on the other hand, provides a roadmap of study that extends beyond the boundaries of personal interest, or familiar recurring problems.
Immanuel Kant first identified the tension between theory and practice, which can be summarized in his own words:
"Experience without theory is blind, but theory without experience is mere intellectual play."
Some folks like to start with theoretical knowledge, and some like to learn in a hands-on fashion. It is a mistake to assume one method is sufficient and stick to it.
Regardless of where you prefer to start, you should be iterating between the two. Practical application gives relevance to your knowledge, and the theory provides context and breadth.... and combined, they are powerful.
Tell all your friends, but not a whole bunch:
So, you've passed your exam, and announced it on Linked-In, but how do you let your teammates know without being a jerk?
Certifications, wielded improperly, can cause rifts with colleagues. If you get a certification, notify your manager, and make a celebratory announcement to your teammates, and never mention it again.
领英推荐
Mentioning more than once could be seen as lording it over others (it is), and is an unpleasant thing to do.
Instead, create just enough awareness to help your team know that you've been investing in your own knowledge, and that you're ready and able to step into new challenges.
Conversely, don't hide your accomplishment out of unnecessary humility. Your teammates and managers need to know what contributions you're able to make.
My certification process:
I've gotten very methodical about how I certify, turning it into an easily repeatable workflow:
On cheating:
My first IT certification was in 2001. Since then, I've seen a gradual increase in the security of the testing centers, in terms of what one can take in to an exam, what one wears, and the degree of scrutiny. These provide hints as to how cheating is being done.
By 2015, I was seeing physical searches of my person I hadn't seen before, including a pat-down.
By 2022, I had to remove any extra articles of clothing. No sweater, no hoodie, no shawl, no hat. Just shirt, pants. Mildly uncomfortable if one tends to be cold, as I do.
It's a gradual escalation of measure, countermeasure. It's my personal belief that there are massive online ecosystems dedicated to cheating.
Things have gotten more interesting with the advent of online proctoring, and it's vexatious and cumbersome security theatre. (Looking at you, Hashi).
Is the effort to cheat less than the effort to study? Clearly, it is happening, but ethics aside, it does not even seem economical to me.
Plus, it deprives you of those dopamine hits that come with "I understand this now!"
Tips and Caveats:
Happy Certifying....
--
Credits: This image generated by DALL-E using the prompt “Please generate an image of a man surrounded by many IT certificates in the style of Dali”.
A statement on consistency: After a day at work, and an evening of driving my daughter on errands, and boosting neighbor's cars, and of finishing this article, I'm tired. But, still made time to review a chapter of the Grafana course I'm studying. Only 10 minutes. Baby steps, right?