Modern programmers live in a very special period of time, when the software is penetrating into literally all spheres of human life and is installed on a numerous amount of devices that are a part of our every day life. Nobody is surprised by software in the fridges, watches and coffee-machines. However, the dependence of people on the smart technology is also growing. The inevitable consequence: the reliability of the software becomes priority number 1. It’s hard to scare someone with a freaked out coffee-maker, although it can bring a lot of harm (liters of boiling coffee flowing on your white marble countertop…). But the thought of growing requirements for the quality of software is really important, that’s why let’s talk about errors in the code that led to significant waste of time and money.
The aim of these stories is to fight against the idea that defects in programs can be treated as lightly as they were before. Errors in programs now aren’t just incorrectly drawn units in a game, the code is now responsible for people’s health and safety of property. In this article I would like to cover several new examples of the necessity to treat code really thoughtfully.
[It appears that the submitter of this story is also the author of the linked story. We generally try to avoid such items as it could very well lead to a submission queue stuffed with self-promoted articles. As it is the weekend, I thought I would try this story out as an experiment. Feel free to opine in the comments. --martyb]
(Score: 0) by Anonymous Coward on Sunday July 02 2017, @03:41AM
Can't be done, not even once they finish upgrading the big doughnut in 2047. You're talking about surviving a journey with a divergence over 80%! I doubt there'd even be a solar system there much less an Earth!