One Article Review
| Source |  NoticeBored |
|---|---|
| Identifiant | 412870 |
| Date de publication | 2017-09-28 13:46:22 (vue: 2017-09-28 13:46:22) |
| Titre | NBlog September 28 - safe & secure |
| Texte |  The Coming Software Apocalypse is a long, well-written article about the growing difficulties of coding extremely complex modern software systems. With something in the order of 30 to 100 million lines of program code controlling fly-by-wire planes and cars, these are way too large and complicated for even gifted programmers to master single-handedly, while inadequate specifications, resource constraints, tight/unrealistic delivery deadlines, laziness/corner-cutting, bloat, cloud, teamwork, compliance assessments plus airtight change controls, and integrated development environments can make matters worse. Author James Somers spins the article around a central point. The coding part of software development is a tough intellectual challenge: programmers write programs telling computers to do stuff, leaving them divorced from the stuff - the business end of their efforts - by several intervening, dynamic and interactive layers of complexity. Since there's only so much they can do to ensure everything goes to plan, they largely rely on the integrity and function of those other layers ... and yet despite being pieces of a bigger puzzle, they may be held to account for the end result in its entirety.As if that's not bad enough already, the human beings who actually use, manage, hack and secure IT systems present further challenges. We're even harder to predict and control than computers, some quite deliberately so! From the information risk and security perspective, complexity is our kryptonite, our Achilles heel.Author James Somers brings up numerous safety-related software/system incidents, many of which I have seen discussed on the excellent RISKS List. Design flaws and bugs in software controlling medical and transportation systems are recurrent topics on RISKS, due to the obvious (and not so obvious!) health and safety implications of, say, autonomous trains and cars.All of this has set me thinking about 'safety' as a future awareness topic for NoticeBored, given the implications for all three of our target audiences:Workers in general increasingly rely on IT systems for safety-critical activities. It won't be hard to think up everyday examples - in fact it might be tough to focus on just a few!With a bit of prompting, manager |
| Envoyé | Oui |
| Condensat | author since 100 about account achilles activities actually add adverse airtight all already analysts another anyway apocalypse appreciate architects are around article aspects assessments associated audience audiences:workers author autonomous awareness bad being beings best bigger bit bloat bring brings bugs bulging burgeoning business but can cars central challenge: challenges change chaos cloud code coding coming complex complexity compliance complicated computers constraints continue control controlling controls critical cutting deadlines deliberately delivery design despite development difficult difficulties discussed divorced doing doubt drafting drawn due dynamic effects efforts end enough ensure entirety environments etc even everyday everything evolve examples excellent extremely fact flaws fly focus from function further future general get gifted given goal goes growing guidance hack handedly hard harder has have health heel held hopefully how human illustrated implications inadequate incidents includes including increasingly information integrated integration integrity intellectual interactive intervening introducing its james just kryptonite large largely layers laziness/corner least leaving lines list long make manage managers many master materials matters may medical might million mind: minimize modern much nblog not noticebored numerous obvious only operational order other others outline part perspective pieces plan planes plus point portfolio pragmatic predict present prevent professional program programmers programs prompting puzzle quite readily real recurrent related rely researching resource result risk risks rough safe safety say scope secure security seen september set several sharp should simplicity single situations software software/system some somers something specialists specifications spins stuff subject systems talking target teamwork telling testers than that them them;the then there these things think thinking those three tight/unrealistic today too topic topics tough trains transportation treat use way ways welcome well when which who will wire won world worse would write written wrong yet |
| Tags | |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.