One Article Review
| Source |  NoticeBored |
|---|---|
| Identifiant | 2165023 |
| Date de publication | 2021-01-10 10:34:21 (vue: 2021-01-09 22:05:32) |
| Titre | Y2k + 20: risk, COVID and "the Internet issue" |
| Texte |  It feels like 'just the other day' to me but do you recall "Y2k" and all that? Some of you reading this weren't even born back then, so here's a brief, biased and somewhat cynical recap.For a long time prior to the year 2000, a significant number of software programmers had taken the same shortcut we all did back in "the 90s". Year values were often coded with just two decimal digits: 97, 98, 99 ... then 00, "coming ready or not!"."Oh Oh" you could say. "OOps".When year counters went around the clock and reset to zero, simplistic arithmetic operations (such as calculating when something last happened, or should next occur) would fail causing ... well, potentially causing issues, in some cases far more significant than others.Failing coke can dispensers and the appropriately-named Hornby Dublo train sets we could have coped with but, trust me, you wouldn't want your heart pacemaker, new fangled fly-by-wire plane or the global air traffic control system to decide that it had to pack up instantly because it was nearly 100 years past its certified safe lifetime. Power grids, water and sewerage systems, transportation signalling, all manner of communications, financial, commercial and governmental services could all have fallen in a heap if the Y2k problems wasn't resolved in time, and this was one IT project with a hard, immutable deadline, at a time when IT project slippage was expected, almost obligatory. Tongue-in-cheek suggestions that we might shimmy smoothly into January 1st [19]9A were geekly-amusing but totally impracticable. In risk terms, the probability of Y2k incidents approached 100% certain and the personal or societal impacts could have been catastrophic under various credible scenarios - if (again) the Y2k monster wasn't slain before the new year's fireworks went off ... and, yes, those fancy public fireworks display automated ignition systems had Y2k failure modes too, along with the fire and emergency dispatch systems and vehicles. The combination of very high probability and catastrophic impact results in a risk up at the high end of a tall scale. So, egged-on by information security pro's and IT auditors (me, for instance), management took the risk seriously and invested significant resources into solving "the Y2k issue". Did you spot the subtle shift from "Y2k" to "the Y2k issue"? I'll circle back to that in just a moment. Individual Y2k programming updates were relatively straightforward on the whole (with some interesting exceptions, mostly due to prehistoric IT systems still in use well past their best-before dates, with insurmounta |
| Envoyé | Oui |
| Condensat | that did flip hey in individual make so some the tongue you 100 1st 2000 20: 90s about accurate acknowledge adamant adequate again ahead air all almost alone along although amount amusing and another apart appreciate approached appropriately architectures are area areas aren arising arithmetic around ascendance ask asking aspect assessed associated auditors automated away back bad baling because been before beige being believe best better biased big blame blending blue born both boxes brief busy but button calculating can cases cataclysmic catastrophic causing certain certified cesspit chain challenge change cheek chips circle click clock cloud coded coding coke combination come coming commercial communications comprehensive computer computers computing conditioned connections considered conspiracy containing control coped copped cops corrected cost costly could counters counting covid covid19 created credible crisis critical cultural customers cynical daddy date dates day deadline debacle decade decades decide decimal defence definitely deliberately demonstrate dependencies dependent depends design designed desktops despite destined details development device devices diagrams did did back dig digits: digress disaster disastrous discovered disease dispatch dispensers display disruptive documented dominating don done draw dublo due during effort egged embedded emergency encoding end enormous enough ensure entire episode etc evaluating even ever every everyone everything everywhere exceptions expand expected expediency expense face facing fail failed failing failure fake fallen fancy fangled far fast feels financial finding fire fireworks firing firmware fixing fleece fly following fore form forward found from future gave geekly general generalise get global golden gone governmental grids had happened happy hard hardware has have heading headlines health heap heart here heroes hidden high history hold home hornby horribly horrors how humming ibm identifying ignition ignorance immutable impact impacts implemented impracticable incident incidents including increasing indistinct industries industry industry: information infosec infrastructure instance instantly instead insurmountable intended interesting internet inventory invested investment iot isn isolating issue issues issue|problem|risk|crisis its january jobs jokes just know known labels large last latest leadership least leaves let life lifetime like limitations line linked lockdown long longer looking lull machines mainframe maintenance major making management manner manufacturers massive maybe meaningful meanwhile media mentioned might missed mission mobility mode models modes moment money monster more mostly mounting myriad named namely nature nearly necessary network never new news next nor not now number numbers obligatory obvious obviously occur off often once one only oops opened operations opportunity organisation organisations organizations other others out over own pacemaker pack pandemics parallel particularly past people personal pertinent place places plane planet plans plot policies portrayed possibly potentially power prehistoric pressed presumably prevent prevented prior pro probability problem problems processes professional profiles programmers programming project proliferated proliferating pros public publish pundits rant rather reading ready real really reasonably reasons recall recap relatively relief remain remediation/replacement remember repeat replacing rescue reset resolved resources results revisions right risk risks safe same sanctuaries saved saw say scale scenarios scope sealed securing security see serial seriously services sets sewerage sheer sheer scale of shift shimmy ship shortcut shortcuts should show sighted signalling significant similar simplistic simply simply finding all since single situation slain slippage slipped smoothly societal society software solution solving some something somewhat soon sorry spot status st |
| Tags | Guideline |
| 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.