That's already not the case. Lawyers can get in shit for giving bad advice, and architects have to sign off on blueprints for things that matter.

That doesn't mean that lawyers can't make jokes and architects can't draft blueprints for buildings that smoosh every occupant; it means their professional statements have legal weight.

There are regulations that affect the work of software engineers. PCI DSS is one that I am familiar with. Perhaps unfortunately, if your software interacts with the real world (like payments infrastructure), you have to heed regulation. This tends not to affect people who are casually writing software or working on many open source projects, but it does impact large companies like Google.

(I like to think of this as pretty similar to the Haskell IO monad. At some point you have to break out of your cozy side-effect free code and actually do something. At that point you have to deal with the messy real world.)