Lunduke
News • Science & Tech
The story of the first "computer bug"... is a pile of lies.
A fun, endearing, delightful pile of lies.
August 28, 2023
post photo preview

Many of us have heard the story of “The First Computer Bug”. It goes something like this…

On September 9, 1947 — at 3:45pm — Grace Hopper recorded the “first actual case of a bug being found” in her logbook. The bug was a moth found between the relay contacts of the Harvard Mark II computer.

The story is a fantastic one. A bug. An actual bug causing a computer to misbehave.

The fact that this was found by Grace Hopper — who is an absolute legend in the world of computer programming — adds to the legendary status of this story. And this story has been repeated countless times as the origin for why we use the term “bug” when talking about errors and defects in computer software.

Here is a picture of the actual log book page. Note that the moth in question is actually taped onto the page. Which, I must say, is a pretty awesome way to handle a “bug report.”

Photo of the log book from 1947.

So that you can get a full appreciation for the computer we’re talking about here, this is what the console of the Harvard Mark II computer looked like. Note the teletypes to either side of the desk

The Console of the Harvard Mark II. Image courtesy of Gwen Bell.

See that cool control sitting in the middle of the table? Here’s a close up view of that beauty. Just because.

Photo courtesy Smithsonian.

And what about those relays where that moth was found? Well. Here is a picture of the bank of relays of the Harvard Mark II. This is where the moth was discovered.

Photo courtesy Smithsonian.

Petty cool right?

And a cool story! The origin of the “computer bug”! By Grace Hopper! Awesome!

A story so cool that it has been repeated (with ever so slight variations) in so many major publications. Everything from the New York Times to Newsweek has repeated this anecdote. Telling this story in computer publications is almost a sacred tradition at this point. Such as in the January, 1984 edition of BYTE (which has a truly fantastic magazine cover).

 

Note this retelling of the story references the Harvard Mark I instead of the Mark II. Technically both machines existed at this time. But it was likely the Mark II.

There’s just two problems with this story:

  1. This was not the origin of term “bug” being used for engineering — including computer software.

  2. And it was not likely discovered — or recorded — by Grace Hopper.

Seriously.

The two most critical parts of this story — a story repeated more times than almost any other throughout the computing world — are not true. At all.

Let’s start with the logbook.

The likelihood is… that this logbook was not actually Grace Hopper’s. The handwriting does not match Hopper’s — even the National Museum of American History considers this logbook page to not be written by Hopper. And the discovery of the moth in the relay was not Hopper’s discovery either.

Who wrote this logbook entry? That remains a bit of a mystery. One that I would very much like to solve. Considering the relatively small size of the team who worked on the Mark II, I’m hopeful to eventually get a definitive answer to this.

Now. Let’s address the other factual problem with this story…

This is not the first time that computer defects were referred to as “bugs”.

In fact, that was already common at this point — as it had become standard throughout many engineering fields for several decades.

In fact, here is a quote from Thomas Edison — dated March 3rd, 1878 — where he talks about finding a bug affecting his technology:

“You were partly correct, I did find a ‘bug’ in my apparatus, but it was not in the telephone proper. It was of the genus ‘callbellum.’ The insect appears to find conditions for its existence in all call apparatus of telephones” - Edison

Here is a scan of the entire letter from Edison:

In fact, even this is not the first time Edison, himself, used “bug” to talk about engineering defects.

A “bug” was a common issue in Quadruplex Telegraphs in the 1800s — specifically referring to “false signals”. In order to fix these “bugs”, Edison invented something called a “Bug Trap”. Which led to a series of trademark disputes well into the 1920s.

And, by this time, “bug” was quickly becoming a common term for any sort of engineering error or anomaly. As computer creation progressed during the 1940s, the terminology was both well understood and used by those early computer engineers and programmers.

Whoever wrote that famous 1947 log entry — “first actual case of a bug being found” — was making a joke. It was, indeed, the first time a physical, insect “bug” was recorded to be found inside a computer.

  • It was not, however, the first time a joke was made about finding a real “bug” in a work of engineering (that would go to Edison).

  • Nor was it the first time that a computer glitch would have been referred to as a “bug”.

  • Nor was it found or recorded by Grace Hopper.

This has become one of those stories which has been repeated so often — and blindly accepted as fact (in large part, I think, because we have a picture of the actual moth) — that it will continue to be be re-told, over and over again, and never questioned.

Even though it’s filled with falsehoods.

Still. A fun story, though.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
7
What else you may like…
Videos
Podcasts
Posts
Articles
January 24, 2026
Yes, Getting GNOMED is a Thing

gnomed - verb - When installing one piece of software results in the forced install of an entire Desktop Environment.

Example: "I installed a text editor, then my whole system got GNOMED!"

More from The Lunduke Journal:
https://lunduke.com/

00:10:13
January 23, 2026
Xorg's Political Moves Pushes Systems to XLibre

GhostBSD Lead says, "We will release the next release of GhostBSD with XLibre due to the upcoming Xorg rebase."

More from The Lunduke Journal:
https://lunduke.com/

00:16:05
January 22, 2026
KDE Drops Code for FreeBSD Support

The KDE project has removed code to support FreeBSD in their login manager saying, "We rely on systemd/logind, so FreeBSD is not supported."

More from The Lunduke Journal:
https://lunduke.com/

00:10:54
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044
19 hours ago

I’m a Tool Builder

I’m a tool builder. I have always been a tool builder. The last 15 years or so of my career have been away from coding as my main task. GenAI has reawakened not just the coder in me, but the tool builder.

Any time I have to solve a problem for the second or third time, I’m already working on how to build a tool, system, procedure to reduce the amount of time it takes. Back in the day I was very fond of code generators. I used them, and I built my own. I built report generators as well.

I’ve been working with “Ralph Loops” - a technique in GenAI to have a complete list of tasks to accomplish and have the ai code, test, fix, test again (until all tests pass) and keep on going down the list. “Write shippable code while you sleep” is the goal. The reality isn’t quite there. The direction is clear - it’s powerful, it’s super productive. But we are less than two months from the first blog post where Geoffrey Huntley introduced the concept he named the Ralph ...

January 24, 2026

Linux Self Host Up and Running with Cloudflare

Making terrific progress moving off of my hosted vps to a linux box in my home. A looming $350 payment for the next three years was the catalyst for “do I need to pay this, is it time to bring this in house”? I already had the Beelink mini pc, and it’s far faster with more ram than my VPS and the electricity costs are minimal and less than the very reasonable $10/mo of that SSDNODES.COM was charging.

I use docker to partition the vps, and now the Linux Mint machine into “many servers”. When I want to share my work outside my home, that’s where Cloudflare tunnels come in. Exposing ports whether on the vps or on my home router and linux machine is asking for trouble. Cloudflare handles that and more:
Here is the compact definition of what Cloudflare Tunnels provides for your partitioned setup:

  • Inversion of Ingress: Eliminates the need for dangerous port forwarding by establishing a secure outbound connection from your server to the...
post photo preview
January 24, 2026

Very interesting developments...

The Rise of Chinese Memory - YouTube

$89 Lifetime Lunduke Subs ends this week!

Quick heads up, that the $89 Lifetime Subscription to The Lunduke Journal discount ends… at the end of this week!

Discounting Lifetime Subscriptions by over 70% was an absolute blast. So many of you took advantage of the offer that we’re now up to four Lifetime Subscriber walls at the end of every video. Crazy!

But something that awesome can’t last forever. Which means that, in just a few days, Lifetime Subscriptions will return to their regular price of $300.

With no plans to do another wild discount like that any time soon.

So.

  1. If you haven’t already, snag an $89 (via Bitcoin) or $99 (via Substack or Locals) Lifetime Subscription.

  2. Then let me know if you’d like to be added to the Lifetime Wall of Shame Awesomeness.

My guess is, a the current rate, that 4th Lifetime Wall will be full by Friday.

Bonkers.

And, once again, thank you to each and every subscriber. The Lunduke Journal would not be possible without you.

-Lunduke

Read full Article
January 16, 2026
Lunduke Journal Week In Review - Jan 16th, 2025

Whew! It’s been another wild week for Tech News!

Here’s a crazy stat for ya:

We are currently 16 days into 2026, and The Lunduke Journal has already recorded 19 shows (17 of which have been published on every platform, and 2 others to be published this weekend everywhere… but are already available via the MP4 download page). And that’s with taking New Year’s Day off (and getting the flu this week).

It’s a heck of a lot of Tech News, to be sure.

Lunduke’s Top Stories for the Week

If you only have time to watch a few of shows, I recommend these 3 as being the most interesting (or important… or just… strange) from the last week:

In other words: A pretty gosh-darned crazy week for Linux.

(Those links are to Lunduke.Substack.com, but you can watch all of those shows on any other platform. As always.)

Other Tidbits of Awesomeness

A few other notes on this, most excellent, Friday!

And, with that, I leave you with a screenshot of the MP4 listing of the shows so far in 2026. Bonkers.

 

-Lunduke

Read full Article
January 14, 2026
Lunduke's Lifetime Subscriber Wall 3 is almost full!

Holy moly.

This afternoon I sat down to update the 3rd Lunduke Journal Lifetime Subscriber wall — adding in all of you who sent in requests over the last week or so.

And, boy howdy, were there a lot of you! So many, in fact, that the 3rd Lifetime Wall only has room for around 6 or 7 more names (depending on the name lengths)! That’s crazy!

If you want to make it onto “The Lunduke Journal Lifetime Subscriber” Wall number 3… send me an email (bryan at lunduke.com) with the way you would like your name to be displayed.

Or, if you’re not already a Lifetime Subscriber, remedy that for $89. (Which, you know, is a pretty gosh darned good value.) … Then send me that email requesting to be added to the wall.

Once Wall 3 is full, we’ll start in on Wall number 4 (that’s nuts). At the current rate, I expect Wall 4 to debut this week.

And, as always, thank you for your support. Whatever kind of subscription you have, it is deeply appreciated. Monthly, Yearly, or Lifetime. All are amazing. You make The Lunduke Journal possible.

You rule.

-Lunduke

 
Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals