Software Folklore
The article "Software Folklore" by Andreas Zwinkau shares humorous anecdotes about software bugs, inviting readers to contribute their own stories and highlighting similar collections on Reddit and Hacker News.
Read original articleThe article "Software Folklore" by Andreas Zwinkau presents a collection of unusual and humorous anecdotes related to software bugs and glitches. These stories highlight bizarre symptoms and behaviors exhibited by software, such as a car that reacts negatively to vanilla ice cream, printing issues with OpenOffice on Tuesdays, and a missile control system that experiences deadlocks. Other examples include crashes that occur only on specific days, like October 10th or Wednesdays, and peculiar hardware bugs like those affecting hyperthreading. The author encourages readers to share their own stories and mentions that similar tales can be found on platforms like Reddit and Hacker News. Zwinkau also shares links to his blog, where he writes about software-related topics and lists, inviting further engagement from the audience.
- The article compiles humorous anecdotes about software bugs and glitches.
- Examples include bizarre behaviors like a car's reaction to vanilla ice cream and printing issues on specific days.
- The author invites readers to share their own software stories.
- Similar collections of software folklore can be found on Reddit and Hacker News.
- Zwinkau maintains a blog with additional stories and lists related to software.
Related
The weirdest QNX bug I've ever encountered
The author encountered a CPU usage bug in a QNX system's 'ps' utility due to a 15-year-old bug. Debugging revealed a race condition, leading to code modifications and a shift towards open-source solutions.
"Computers Are Useless" and Other Sayings
A collection of quotes by figures like Picasso and Dave Barry humorously and critically discuss computers, programming, and technology's evolution. Themes include limitations, programming challenges, software complexity, and societal impact.
Whose bug is this anyway?? (2012)
Patrick Wyatt shares bug experiences from game development, including issues in StarCraft and Guild Wars. Compiler problems caused bugs, emphasizing the need for consistent tools and work-life balance in development.
Computer Archeology: Exploring the Anatomy of an MS-DOS Virus
The article discusses two former computer enthusiasts who created a benign MS-DOS virus named PARANOID in the early 1990s, reflecting on their experiences and the challenges of accessing old source code.
Be Suspicious of Success
The article emphasizes skepticism towards successful software due to potential hidden bugs, advocating for comprehensive testing of both successful and error scenarios, and recommending resources for further learning in algorithms.
Turns out the PCBs were shock/pressure sensitive, and the debouncing was just a bit off. Reviewers were getting really into their games and mechanically stressing the controllers. Stressed hard enough, the PCB would bend slightly, causing line level fluctuations and eventually ghost inputs. Back in the office we were just doing a job and not getting too emotionally involved in our playtesting.
Some new molds and review units later we shipped the working system. Percussive debugging has solved a number of otherwise intractable bugs over my career.
http://www.catb.org/jargon/html/index.html
and _Zen and the Art of the Internet_
https://www.gutenberg.org/ebooks/34
should be a part of the school curriculum covering the internet.
While specific to the Mac, one wishes:
https://folklore.org/0-index.html
https://www.goodreads.com/en/book/show/40492.Revolution_in_T...
was more widely read (and that it was updated with stories of turning OPENSTEP into Mac OS X), and if there is a similar site for Windows which collected stories such as:
https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
The AI prompting business feels a lot more like the analog circuit where something being "near" something else causes capacitance or inductance without actually being connected.
What is old is again new!
I remember the details being that only on Wednesday did they use the freight elevator to deliver donuts to an all-staff meeting and when they did, the network would fritz.
It turned out that if you move a very large electromagnet (on the elevator) along the network cable, it makes the network go crazy.
Combine that with cable-pullers that rather than putting holes in multiple ceilings and floors in the cable closet, saw that the elevator shaft was a pre-existing hole between floors anyway, simply took the path of least resistance and hilarity (and a real hard network debugging problem) ensues.
Does anyone know when or where this anecdote occurred ?
I immediately geolocated this story.
...my fave:
0015 Ever change the value of 4?
0016 ... Unintentionally?
0017 ... In a language other than Fortran?
Related
The weirdest QNX bug I've ever encountered
The author encountered a CPU usage bug in a QNX system's 'ps' utility due to a 15-year-old bug. Debugging revealed a race condition, leading to code modifications and a shift towards open-source solutions.
"Computers Are Useless" and Other Sayings
A collection of quotes by figures like Picasso and Dave Barry humorously and critically discuss computers, programming, and technology's evolution. Themes include limitations, programming challenges, software complexity, and societal impact.
Whose bug is this anyway?? (2012)
Patrick Wyatt shares bug experiences from game development, including issues in StarCraft and Guild Wars. Compiler problems caused bugs, emphasizing the need for consistent tools and work-life balance in development.
Computer Archeology: Exploring the Anatomy of an MS-DOS Virus
The article discusses two former computer enthusiasts who created a benign MS-DOS virus named PARANOID in the early 1990s, reflecting on their experiences and the challenges of accessing old source code.
Be Suspicious of Success
The article emphasizes skepticism towards successful software due to potential hidden bugs, advocating for comprehensive testing of both successful and error scenarios, and recommending resources for further learning in algorithms.