♊️ GemiNews 🗞️

Demo 1: Embeddings + Recommendation Demo 2: Bella RAGa Demo 3: NewRetriever Demo 4: Assistant function calling

🗞️The Big Crash

🏷️ history 🏷️ history-of-technology 🏷️ crash

🗿Semantically Similar Articles (by :title_embedding)

The Big Crash

2020-11-19 - Marc Cohen (from Marc Cohen - Medium)

Can you imagine the sort of worldwide panic that would ensue if everyone’s smart phone suddenly stopped working? Something analogous happened thirty years ago when, on January 15, 1990, the entire US long-distance telephone network crashed for nine hours.This was a strange, dire, huge event. During the nine long hours of frantic effort that it took to restore service, some seventy million telephone calls went uncompleted.I was working at Bell Labs at the time, which was a subsidiary of AT&T. Limited and isoated failures, akin to modern outages in your ISP’s internet service, were relatively common in those days, however, this sort of ubiquitous and sustained service breakdown taking out the entire network was unprecedented.Bell Labs engineers, working feverishly in New Jersey, Illinois, and Ohio, first tried their entire repertoire of standard network remedies on the malfunctioning System 7. None of the remedies worked, of course, because nothing like this had ever happened to any phone system before.Perhaps the most interesting aspect of the story: the crash of Janurary 15, which happened to be Martin Luther King Day, was not caused by Russian agents, cybercriminals, or hackers. The entire calamity was caused by one line of errant code, written by one very unlucky programmer.As it happened, the problem itself — the problem per se — took this form. A piece of telco software had been written in C language, a standard language of the telco field. Within the C software was a long “do… while” construct. The “do… while” construct contained a “switch” statement. The “switch” statement contained an “if” clause. The “if” clause contained a “break.” The “break” was supposed to “break” the “if clause.” Instead, the “break” broke the “switch” statement.Read the whole amazing story in the article linked below.On January 15, 1990, AT&T’s long-distance telephone switching system crashed. http://www.mit.edu/hacker/part1.htmlOriginally published at https://mco.dev on November 19, 2020.

🏷️ history 🏷️ history-of-technology 🏷️ crash
[Blogs] 🌎 https://marcacohen.medium.com/the-big-crash-d68599693e22?source=rss-1f225b5f22b2------2

🗿article.to_s 

------------------------------
Title: The Big Crash
[content]
Can you imagine the sort of worldwide panic that would ensue if everyone’s smart phone suddenly stopped working? Something analogous happened thirty years ago when, on January 15, 1990, the entire US long-distance telephone network crashed for nine hours.This was a strange, dire, huge event. During the nine long hours of frantic effort that it took to restore service, some seventy million telephone calls went uncompleted.I was working at Bell Labs at the time, which was a subsidiary of AT&T. Limited and isoated failures, akin to modern outages in your ISP’s internet service, were relatively common in those days, however, this sort of ubiquitous and sustained service breakdown taking out the entire network was unprecedented.Bell Labs engineers, working feverishly in New Jersey, Illinois, and Ohio, first tried their entire repertoire of standard network remedies on the malfunctioning System 7. None of the remedies worked, of course, because nothing like this had ever happened to any phone system before.Perhaps the most interesting aspect of the story: the crash of Janurary 15, which happened to be Martin Luther King Day, was not caused by Russian agents, cybercriminals, or hackers. The entire calamity was caused by one line of errant code, written by one very unlucky programmer.As it happened, the problem itself — the problem per se — took this form. A piece of telco software had been written in C language, a standard language of the telco field. Within the C software was a long “do… while” construct. The “do… while” construct contained a “switch” statement. The “switch” statement contained an “if” clause. The “if” clause contained a “break.” The “break” was supposed to “break” the “if clause.” Instead, the “break” broke the “switch” statement.Read the whole amazing story in the article linked below.On January 15, 1990, AT&T’s long-distance telephone switching system crashed. http://www.mit.edu/hacker/part1.htmlOriginally published at https://mco.dev on November 19, 2020.
[/content]

Author: Marc Cohen
PublishedDate: 2020-11-19
Category: Blogs
NewsPaper: Marc Cohen - Medium
Tags: history, history-of-technology, crash
{"id"=>25,
"title"=>"The Big Crash",
"summary"=>nil,
"content"=>"
\"\"

Can you imagine the sort of worldwide panic that would ensue if everyone’s smart phone suddenly stopped working? Something analogous happened thirty years ago when, on January 15, 1990, the entire US long-distance telephone network crashed for nine hours.

This was a strange, dire, huge event. During the nine long hours of frantic effort that it took to restore service, some seventy million telephone calls went uncompleted.

I was working at Bell Labs at the time, which was a subsidiary of AT&T. Limited and isoated failures, akin to modern outages in your ISP’s internet service, were relatively common in those days, however, this sort of ubiquitous and sustained service breakdown taking out the entire network was unprecedented.

Bell Labs engineers, working feverishly in New Jersey, Illinois, and Ohio, first tried their entire repertoire of standard network remedies on the malfunctioning System 7. None of the remedies worked, of course, because nothing like this had ever happened to any phone system before.

Perhaps the most interesting aspect of the story: the crash of Janurary 15, which happened to be Martin Luther King Day, was not caused by Russian agents, cybercriminals, or hackers. The entire calamity was caused by one line of errant code, written by one very unlucky programmer.

As it happened, the problem itself — the problem per se — took this form. A piece of telco software had been written in C language, a standard language of the telco field. Within the C software was a long “do… while” construct. The “do… while” construct contained a “switch” statement. The “switch” statement contained an “if” clause. The “if” clause contained a “break.” The “break” was supposed to “break” the “if clause.” Instead, the “break” broke the “switch” statement.

Read the whole amazing story in the article linked below.

On January 15, 1990, AT&T’s long-distance telephone switching system crashed. http://www.mit.edu/hacker/part1.html

Originally published at https://mco.dev on November 19, 2020.

\"\"",
"author"=>"Marc Cohen",
"link"=>"https://marcacohen.medium.com/the-big-crash-d68599693e22?source=rss-1f225b5f22b2------2",
"published_date"=>Thu, 19 Nov 2020 00:00:00.000000000 UTC +00:00,
"image_url"=>nil,
"feed_url"=>"https://marcacohen.medium.com/the-big-crash-d68599693e22?source=rss-1f225b5f22b2------2",
"language"=>nil,
"active"=>true,
"ricc_source"=>"feedjira::v1",
"created_at"=>Sun, 31 Mar 2024 21:41:11.822917000 UTC +00:00,
"updated_at"=>Mon, 13 May 2024 18:38:10.211627000 UTC +00:00,
"newspaper"=>"Marc Cohen - Medium",
"macro_region"=>"Blogs"}
Edit this article
Back to articles