News for hackers. Stuff that matters.
Re:How the Boeing 737 Max disaster looks to a software Devel... by baddox on Thursday April 18, 2019 @06:13PM (#19695271)
It definitely depends what you're doing. Designing aircraft control systems? Yep, probably strive for perfection. Building a social network site, or a photo-sharing site, or an online forum? You're probably okay sacrificing some level of reliability for iteration speed.
Re:How the Boeing 737 Max disaster looks to a software Devel... by Retric on Thursday April 18, 2019 @06:19PM (#19695310)
It’s less about the domain than the impact of the code.

Bad code can kill your company or go unnoticed, depending on where it is and what it’s doing.

Re:How the Boeing 737 Max disaster looks to a software Devel... by Gibbon1 on Friday April 19, 2019 @02:09AM (#19697436)
I wrote a buggy POS test program that had race conditions because I didn't really understand what I was doing. And sometimes it would assign two units the same serial number. It would check once the test was done and just fail one of the two if that happened. And the tech would just rerun the test on that unit.

In the big scheme of things no one cared.

Re:How the Boeing 737 Max disaster looks to a software Devel... by baddox on Thursday April 18, 2019 @06:29PM (#19695363)
Of course, but the solution for the vast majority of companies and projects isn't "never release code that isn't perfect."