> Seems to work all right for almost every other engineering path such as mechanical and electrical.
I respect your analogy, but I think this is a very incomplete and shallow way of looking at it for just some of these reasons.
> Regardless of however pleasantly you might conceptualize a smart and basic Computer Science exam that you think might not prevent you from working as a dev, there's going to be consequences in the job marketplace and inevitably government overreach that you cannot predict if this emerges. I think this could be catastrophically bad for many developers on a level that we cannot even fully see.
> Software isn't tangible and must move much faster than physical engineering. A bridge or skyscraper might be designed to last at least 100+ years, and can't easily be changed once built. But software is infinitely flexible and can be rapidly changed and adapted to other situations. Rigid thinking in the software domain is much more damaging to progress than in physical engineering.
> With civil engineering for instance, there's a very clear and measurable success and failure condition; basically a structure either handles the load its designed to handle or doesn't. But software is different. A system or an algorithm can be very inefficient and wasteful and "bad" from a software engineering perspective, but still successfully solve the problem and be the right solution from a business perspective. True wisdom in problem-solving through software comes from understanding the tradeoffs involved in building stuff and being able to make the right decision on how to build something, even when it's a "bad" solution "by the book". I don't see a government software engineering test ever being able to capture this.