Re:How the Boeing 737 Max disaster looks to a software Devel...
by anbop on Thursday April 18, 2019 @06:29PM
(#19695362)
Well, great code is inefficient if the impact of bad code is minimal. If you are shipping an animated emoji you should be sloppier with your code than if you are building flight control software. Overengineering software is like over-specing building materials by 10x and spending way more money on a building than it needs.
[ Parent
| on HN ]
Re:How the Boeing 737 Max disaster looks to a software Devel...
by Raidion on Thursday April 18, 2019 @06:37PM
(#19695409)
I agree, but practically a lot of bad software practices happen when middle management don't fully communicate the tradeoffs that are made when designing and building software. I find it hard to believe that this was a problem that no one really saw coming, but just didn't get flagged at a level that was needed to investigate it.
Re:How the Boeing 737 Max disaster looks to a software Devel...
by tremon on Friday April 19, 2019 @05:22AM
(#19698105)
And in that same line of argument, great code is inefficient if the bad code can always be fixed post-release.
Never mind the consequences of the first release, if we sell enough of it we might be bothered to pick up our slack 2 years from now.