So I know there's going to be someone coming in to complain that Software Engineers aren't "real engineers" and we need "real engineering" and real "certifications" so we can be "real engineers"<p>First off I love Jeff Atwood's take on it <a href="https://blog.codinghorror.com/do-certifications-matter" rel="nofollow noreferrer">https://blog.codinghorror.com/do-certifications-matter</a>.<p>But I recently just passed my CISSP, had to for work, and it was one of the most obnoxious and pointless exercises I ever engaged. Most of the test involved questions about information that is hopelessly out of date, or incredibly pointless whose only value is for ivory tower PhDs to argue about in white papers whose only actual security experience is putting in their password to their laptop.<p>I used to be sympathetic to an extent about the value of having a professional certifying body for software engineers, or something like that. Especially after having to debug JS by "full stack developers" who had just become "software engineers in 6 weeks". But after the CISSP racket I am enduring, I've realized a certfying body won't make software developers any more capable, it will only allow those who are the least qualified, to force arbitrary and capricious requirements onto people who actually care about the craft and are capble.<p>/rant over.