There are some important additional steps, in that mgmt can't just hire any bum off the street to be a fall guy psuedo-P.E.. There is a mutually accepted and understood system where the very boring and static profession can be verified by mere years of experience (all jobs being similar) and a test no one seriously argues about based on what everyone agrees is very typical work for a P.E.
I can't even begin to imagine the sheer flamewar load even thinking about a "professional programmer" certification would cause.
I always liked the idea of an apprenticeship - journeyman - master system. It sidesteps the theoretical definition of what is a masters work by simply having existing masters vote to see if you make the cut, or not. Master level work in the field seems like it should be inherently different in the center of the CRUD app universe vs the center of the financial universe vs the center of the aerospace universe, for example.
In Canada, the test required to be passed to obtain the PE license does not have a single question concerning actual matters or competency. Rather, it concerns the legal framework, the deontology, the ethics and the responsibilities of the profession.
The obligation of competency is part of the Deontological Code. Or at least, so it is in Quebec. The Engineer (note that Engineer is a legally reserved title in Quebec, rather than "Professional Engineer" in most other places) is obligated to perform mandates only if he is competent do to them. It is his own resposibility to make sure he's competent.
If he is later shown to have performed work for which he was incompetent, he is liable to fines and/or to have his license revoked temporarily or permanently.
The PE licensing system here also requires a certain period (3 years) under which the EIT (or jr engineer in QC) must work under the direct supervision and direction of a licensed PE, before applying to obtain his PE license. This is similar to the apprenticeship system you propose, from what I understand.
I can't even begin to imagine the sheer flamewar load even thinking about a "professional programmer" certification would cause.
I always liked the idea of an apprenticeship - journeyman - master system. It sidesteps the theoretical definition of what is a masters work by simply having existing masters vote to see if you make the cut, or not. Master level work in the field seems like it should be inherently different in the center of the CRUD app universe vs the center of the financial universe vs the center of the aerospace universe, for example.