News for hackers. Stuff that matters.
Re:Programmers who want to change how we code before catastr... by tener on Wednesday September 27, 2017 @02:39PM (#15350912)
Broken software does not typically kill people or makes you loose money (time or some other resources, maybe).

In contrast bridges that fall apart tend to kill people in a nasty way. They are also quite hard to reboot.

Re:Programmers who want to change how we code before catastr... by Bartweiss on Wednesday September 27, 2017 @02:52PM (#15351076)
An excellent framing I saw recently was "I can tell the people who write these articles don't actually want secure code, because they aren't paying me to write it."

There's plenty of carefully-written, rigorously-tested code out there. Want to write software for air travel, drug manufacturing, or space flight? You'll have no choice but to write safe, first-rate code.

Want a smartphone weather app written to those standards? Well, for $50 and a feature set five years behind the state of the art, you can have it.

Re:Programmers who want to change how we code before catastr... by blackth0rn on Wednesday September 27, 2017 @03:40PM (#15351515)
Isn't this a tooling and knowledge issue? If I was as productive with TLA+ or model based design as I am with React-Native/Ionic/Swift etc. then we could have a smartphone weather app written to those standards for the same price.
Re:Programmers who want to change how we code before catastr... by hwayne on Wednesday September 27, 2017 @04:17PM (#15351876)
While there's plenty of room for improvement, I legitimately believe that TLA+ is now in a place where it's convenient enough to use in conjunction with Ionic/Swift.
Re:Programmers who want to change how we code before catastr... by IncRnd on Wednesday September 27, 2017 @03:29PM (#15351422)
Broken software has the capability to regularly kill people or cause people to lose money. It happens too often.