> Engineers don't work with infinite budgets and they usually are not the people who are making final decisions on either maintenance or implementation.
There are plenty of examples where the problems as the design, not the implementation, such as:
https://en.m.wikipedia.org/wiki/Hyatt_Regency_walkway_collap...
Different projects have different costs for failure. A bridge failure costs more than a child's toy that breaks. A browser tab crashing costs less than a mars orbiter that burns up in the atmosphere. Engineering isn't confined to just working on things where people die or stuff explodes if you mess up.
Engineers don't work with infinite budgets and they usually are not the people who are making final decisions on either maintenance or implementation. Many of these failures occur because of budget constraints, time constraints, or decision makers who go against the recommendations of experts.
IMO, the closest thing to a "software engineer" is a software architect. Everyone else is a craftsman.