It's beyond traditions in some regions as well. For example, in Canada, the "engineer" title is protected, so anyone using that title must be a registered member of the provincial association (wherever they practice).
Do you think an engineer just sits down, draws your bridge up after some math and then builds it? It takes a team of civil engineers multiple iterations with tests, setbacks, feedback loops etc to get to the final design.
Software can also come with the same type of warranty you imply here. I'm reminded of this image https://media.boingboing.net/wp-content/uploads/2017/04/sd72...
If an engineer designs my bridge, and it collapses when more than one car is on it, he can't laugh at me for not giving him a spec that included that requirement. Contrast this with software, where if a database stores plaintext passwords, the programmers are probably protected if there is sufficient documentation that the bosses/customer insisted on it.
I'm grateful to have the flexibility of creating effectively magical things that can change easily to meet changing requirements, but I also feel like there will come a time when we will need to have some similar degree of engineering rigor mandated for software.