> Companies don't care about it. We carry on as is...
If required by law, companies would care.
> This is a classic over-engineered solution that nobody wants to a problem that barely exists.
The sorry state of our industry means the opposite: the problem is big, but lack of teeth means companies can ignore it and externalize the costs.
> Just add burocracy, what could possibly go wrong...??
I'd prefer to create our own bureaucracy, not have governments push one on us, like the Cyber Resilience Act does in the EU.
We've had professional certifications for years. Novell, Citrix, Microsoft, SAP, Oracle, they all make money selling certification to naive users. Anyone who's bothered knows they don't really mean much.
But hey, if you think there's demand, set up a body and give it a go. Personally I think it's a waste of time, but if you can get enough companies to care, and enough developers to pay, you'll have a nice business.
Herding cats sounds easier.
So, historically the creation of bureaucracy in the US government included industry professionals to guide the requirements and a public comment period before finalization. This is done because most people in government recognize they are not up to date on the latest industry knowledge.
Destroying everything and creating a new bureaucracy is in absolutely no way better than fixing the original one on updated information.
It seems you may have fallen victim to the very well thought out "government bad!" argument.
Here's what'll really happen; no one cares or wants yo be a certified professional. Companies don't care about it. We carry on as is...
This is a classic over-engineered solution that nobody wants to a problem that barely exists. Just add burocracy, what could possibly go wrong...??