Skip to main content

1,000 (bad) ideas

Tidying up my messy corner in the basement I unearthed one of my older "ideas books" in which I write down the random ideas that flit through my head quite frequently. Flicking through it I noticed that this book contained idea number 1,000 written on October 3, 2006. Most of these ideas never get implemented but they are fun to go back and read.

Idea 1,000 was In-ear headphones that automatically pause music when removed. The details mention using either a proximity detector to discover when the headphones are in the ear, or a strain gauge to detect the pressure of the ear canal.

The previous idea was Brake lights that show the severity of braking. The idea there was to replace the current 'high-level' brake lights in cars (that are typically a horizontal bar), with a triangle of lights. Under normal braking just the top, horizontal red bar would illuminate. Under heavy braking the triangle would illuminate warning drivers of an emergency situation (particularly useful on motorways at high-speed). Since the red triangle is a common warning symbol this would be instantly recognizable.

I've been filling these books since about 1992. By 2006 I'd had 1,000 (bad) ideas, which works out to about one every five days. Some of them I've implemented (such as l8tr), others I've seen implemented by other people: there's an amusing entry from 1995 about building a networked disk drive service that I wanted to call "I-Drive". The plan was to use FTP as the underlying protocol and make a drive (I:) appear in Windows 95. I: would actually be on the Internet and could be accessed by multiple machines.

The idea I'm most pleased with is my book, The Geek Atlas, because it was (fairly) original. No one else had written "Lonely Planet for Nerds". Overall, perhaps 10 of my 1,000 ideas look like they might be 'good ideas'.

Does anyone else generate ideas like this? And if so, what percentage turn out to be good?

Related Hacker News discussion


Rors said…
All the time.

0% success rate currently :)
Thomas B said…
I don't know that I have had a thousand, but I do this, as well. My best ideas are the one's which attempt to solve my everyday problems.

The most notable for me was a bookmarking service that would replicate bookmarks across computers and browsers, which is what I use delicious for. I had that idea in the mid-to-late 90s I guess and that probably was already a stale idea then. Doh! Delicious was either in existence or started not too long after that.

Again a reason to not wait and simply create your solution. Other people are bound to have a similar need.
Paolo G. Lim said…
this sounds like a very nice habit to form. i often think of random ideas especially on boring commutes. then when i get home, i just forget everything. such a waste! i better buy a notebook now!

thanks for the tip!
Ruben Berenguel said…
I don't write them down, but I generate ideas... and most die within my own brain. I still remember being a teenager (around 13 or 14, considering which book I remember reading back then) and thinking that if sound was a wave, you could build an earphone with a microphone generating the reverse sound, thus making all silent. I thought wow, that should be cool! And 3 years later I read "how do noise cancelling earphones work" in SciAm... I didn't know what to think about that ;)

I think this idea of writing down the stream of ideas may be interesting... but I think the big failure rate would put me down pretty quickly.


Latest in my blog: 33 Best Blog Posts I Have Read in August, 2010
Adam Conrad said…
WHAT!!! That's crazy, I came up with the same idea for brake light severity. I called them Cascading Brake Lights, and basically the brake light turned into a grid of LEDs. As you applied more pressure, the grid would rise, so if it was a 5x5 grid, light breaking would light up the first row, where severe braking would light up all 5 rows. I had a patent ready to be filed, but after speaking with a few patent lawyers and professors, the market seemed too difficult to penetrate simply because the introduction to the public would be difficult, coupled with it being difficult to see the differences, even at relatively close quarters, such as a traffic jam.

Cool to hear someone else was thinking the same thing!
Matt Williamson said…
yeah, my brother in law wanted to patent spray bottle eye drops and then Visine came out with them. For you, the brake light levels have been implemented by BMW.
Bob Hazard said…
I had an idea in the 90s for a car alarm that sends you a text message. You can get them for home windows and doors now too.

I could have been rich
danio said…
I remember a few years ago my mother mentioning that a 1950s or 1960s car had an array of brake lights that showed braking intensity. Unfortunately a quick web search doesn't find anything.
Also I remember my dad suggesting orange warning lights to show when the driver has taken their foot off the accelerator (so may be about to brake). And then orange was chosen for turn indicator lights.
Unknown said…
@Ruben - Those noise cancelling headphones were actually 'invented' in an old sci-fi short story.

I can't remember the name or author (possibly Heinlein), but I actually set about to build some years before they actually came to market.

I failed, but transistors just weren't fast enough then. The author should have patented the idea though. :)

I remeber the first time I saw them in the 'whats new' section of popular science, and just about cried.
Unknown said…
@Emonk: "Silence Please" by Arthur C. Clarke.
Anonymous said…
I've had a number of ideas that ended up being implemented months or years afterwards by others. The latest I've come across is Bing Rewards, though my version of it was on a much bigger scale.

I like the idea of writing down every single idea as it forms. That's a habit I'm going to cultivate.
Unknown said…
Any thought on making this entire notebook available? I'd like to see some more of your ideas, I'm fascinated by ideas that will never see the light of day.
I probably should make more of them available. Just need to find the time.

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of