You can certainly blame the builder, but the "real" engineers I've talked to all spoke of traditions like a _ring on their pinky_ so that when they are signing their name to a design, they are reminded (as the ring touches paper) that their signature affects real people's lives, and that both their professional reputation and personal liability might be on the line if they screw it up.
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.
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.
That's actually quite rare and certainly in some engineering disciplines no way would you wear a ring whilst working for H&S reasons I am thinking of EE and Mech here.
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.