I think with regards to certifications it's a matter of where you are in your career and what your expectations are from them.
When you start out in your career I think: it gives you basic understanding of some concepts you will be working with, it shows recruiters and potential employers you are serious about your career and professional development and it will make you assimilate the working knowledge faster. At this level the certification will of course not replace actual working knowledge, it just sets your foundation and it will be up to you how you proceed next.
When you move on in your career and already have working experience it could be good to get certified not for the certification itself but going through the documentation and preparation for the exam. You might learn new things and best practices. At this point you are just refining your knowledge.
What I would say is:
don't get certified for the sake of accumulating certifications (instead try to build a professional profile)
don't get certified on things you are not or will not use
certifications are not a must I feel. Try working on building a portfolio, do small projects etc those are a great way to learn something new or try something out
It may be just your 2 cents but it is such real advice, @the_cozma! Certs for the sake of certs instead of building professional profiles makes so much sense.
It may seem obvious to some, but for fresh graduates who have been immersed in education their whole lives without a ton of work experience, chasing certification can become a bit of a comfort zone.
Thanks for this gentle reminder that it's important to build a professional profile, even without having official "work" experience: learning in public, contributing to open source, all these things can help fill in gaps in employment.
For further actions, you may consider blocking this person and/or reporting abuse
We’re an inclusive community for sharing DevOps and SecOps tips & tricks, tutorials, and career insights.
I think with regards to certifications it's a matter of where you are in your career and what your expectations are from them.
When you start out in your career I think: it gives you basic understanding of some concepts you will be working with, it shows recruiters and potential employers you are serious about your career and professional development and it will make you assimilate the working knowledge faster. At this level the certification will of course not replace actual working knowledge, it just sets your foundation and it will be up to you how you proceed next.
When you move on in your career and already have working experience it could be good to get certified not for the certification itself but going through the documentation and preparation for the exam. You might learn new things and best practices. At this point you are just refining your knowledge.
What I would say is:
Just my 2 cents on the matter
It may be just your 2 cents but it is such real advice, @the_cozma! Certs for the sake of certs instead of building professional profiles makes so much sense.
It may seem obvious to some, but for fresh graduates who have been immersed in education their whole lives without a ton of work experience, chasing certification can become a bit of a comfort zone.
Thanks for this gentle reminder that it's important to build a professional profile, even without having official "work" experience: learning in public, contributing to open source, all these things can help fill in gaps in employment.