Formal licensing could be about things that are language agnostic like how to properly use tests to guard against regressions, how to handle error states safely.

How do you design programs for critical systems that CANNOT fail, like pace makers. How do you guard against crashes? What sort of redundancy do you need in your software.

How do you best design error messages to tell an operator how to fix the issue, especially in critical systems like a plane, and guard against them doing the wrong thing. I’m thinking of the DreamLiner incidents where the pilots’ natural inclination was try grab the yoke and pull up, but that caused the plane to stall. My understanding was that the error message that triggered during those crashes was also extremely opaque.

When do you have an ethical responsibility not to ship code?

None of that is impacted by what tech stack you are using.

Lastly, under certain circumstances, Civil engineers can be held personally liable for negligence when their bridge fails and people die. If we are going to call ourselves “engineers”, we should bear the same responsibility.