Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Sunday July 02 2017, @12:27AM   Printer-friendly
from the eventually,-it's-always-the-consumers dept.

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]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Unixnut on Sunday July 02 2017, @09:59AM

    by Unixnut (5779) on Sunday July 02 2017, @09:59AM (#534137)

    Indeed, in my previous employment they were known as the "sacrificial lamb", and it worked pretty much as you say it does.

    Best thing (for the company) is the wronged employee would be wise to not sue for constrictive dismissal, even if they had a case. If it comes out that you sued your former employer (and as lawsuits are public record, easily to find online) you will never get another job. The moment a new employer sees you sued your previous one, they will think "High risk, might sue us, not worth it", and move to the next candidate.

    So you basically have to suck it up, unless you got a) an ironclad case, with evidence, and b) money to get some really really good lawyers, in which case you sue for enough money to keep you all set without ever having to work for the rest of your life, if you win that is.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2