Decided to listen to this one first even though another episode brought me here. Sounds like I am on the right track before I listened to this. Not to belabor the point, my viewpoint is to get certified to support and supplement my other skills from the last century even though my current work is not using AWS. Instead of the certificate being the focal point, I make applying the AWS skills a priority so that I can speak to the experience. My fate has always been that I mess up something, and I have to figure out how to resolve it. I already came to the conclusion that just about every training material is set up as if nothing goes wrong. I leverage my past experience to bridge the gap that the training material might not cover. Generally speaking, some books out there point out traps and pitfalls which makes the material more valuable to me. As for the comment about the 1,000 getting certified that have not gone through the pitfalls, I say, let them experience it. That will separate those that are willing to be uncomfortable and learn from it, from those that are instantly frightened and already rethinking their choices that led them to that point. As with any industry, there are those that know their stuff and there are those that are just getting by and only in it for the fame and glory. Looking forward to catching up on your past material and looking forward to the upcoming ones. Thanks.

Thank you so much for the 5 reasons why we should not certify AWS. I totally agree with you, and I also find through blogs, Twitter, GitHub and other open projects are better the skills to refer instead of a certification. But most customers and recruiters are unfortunately not yet able to measure such resources. And they want to show the easiest certificates.