I think there are bigger guarantees and checks the beam works as it's specified so the next engineer can continue.
Google was using in production (firebase cli) the notorious trick the js developer played us other week. I doubt the other fields would rely on some random developer from Australia who has had a colorful past to provide the beam for structural engineer. And there's definetly more testing from all sort of parties they work om real life as advertised.
Then again no one is offering free open source beams and you can't since you need materials not just one time drawings of an idea.
Re:Are We Really Engineers? (2021)
by netizen-936824 on Wednesday January 19, 2022 @05:37PM
(#30001410)
The beams may not be open source but the calculations are
If the beam is in a critical application, it may have provenance, or a material history, for similar purposes.
In software, the range of correct operation (eg: maximum web server load with response time under x ms) is commonly unspecified and omitted. The strength of the beam gives a conservative estimate of its capabilities. Still a model/abstraction, but one with boundaries.
Re:Are We Really Engineers? (2021)
by Scramblejams on Wednesday January 19, 2022 @07:11PM
(#30002385)
The difference (if any) between simplification and abstraction is the subject of some debate!
While I fully agree with almost everything in your post, this sounds an awful lot like an abstraction to me. Perhaps the different between creating software and engineering based on the physical sciences is the degree in which the abstractions are understood and rigorous. Perhaps software engineering is simply in its infancy and may eventually lead to more rigorous designs with less or no bugs in the future?