3 ms·
If you think of code as infrastructure, it's not insane, it's the expected outcome. Bridges were built differently in the 1960s than they are today. We are not
by semi-extrinsic 4y ago
If you think of code as infrastructure, it's not insane, it's the expected outcome.
Bridges were built differently in the 1960s than they are today. We are not tearing down all the old bridges and building new ones, that would be crazy. Instead we need to spend enough time and money on maintenance of the old bridges, and replace them when that becomes the better option. When we fail to conduct proper maintenance, accidents happen, like Ponte Morandi.
- devwastaken 4y agoOld bridges are being replaced all the time. Modern bridges aren't built like the 1960's anymore, yet with code it's like we're still in 1990 when a new project starts.
- pjmlp 4y agoWe are taking people to court that build broken bridges.
- nix23 4y agoWe aslo bring people to court who endanger/kill peoples per software-(bugs)... I also have seen many bridges where no responsibility can be assumed (especially in the mountains).
- pjmlp 4y ago> We aslo bring people to court who endanger/kill peoples per software-(bugs)... Only in high integrity computing scenarios. All kinds of refunds and lawsuits from physical goods should apply to software as well. Regarding the bridges, just because "guilt died alone" as we say back home, doesn't mean we should disregard the bigger picture.
- timeon 4y agoUnlike software, civil engineering is subjected to regulations.