Tell YC: The gap between idea and starting development - the longer the better. | Hacker News Reader

Tell YC: The gap between idea and starting development - the longer the better.

15 pointsagentbleu17 comments

I have been pondering away over an idea that I had a few months ago, I was writing a blog post about a problem when I had the aha moment, thus, I abandoned the blog post and started conceiving the new application. I spent a week knocking up some rough drafts to explore the technical problems and then got side tracked with another few projects that emerged and needed immediate attention. Since the conception a few months ago, there has been a wealth of other blog articles that have reinforced my initial belief that a desire exists for such an app, but more importantly I have been able to ponder what would be the best way to develop the concept. It's a complicated application so the time to reflect with ones mind open to the challenge while figuring out 'best possible solutions'. As a result I am starting back now on development but with more confidence in the concept and a better understanding of how to best execute the conception. Thus the moral of the story, have an idea, then sit on it for a few months to let the collective blogsphere to fuel the concept with elements that could well make all the difference between a killer app or dead donkey.

"Real artists ship." --Steve Jobs

But seriously, from what I've seen, iteration is the best way to give birth to something real and useful into the world. There are just so many scenarios and edge cases that you will never think of until:

1) You're actually coding it 2) A real user is actually using it and fails

If two people of equal skills have the same idea and one starts coding and the other sits back to ponder the idea some more, my take is that the do-er will 9 out of 10 times beat the thinker.

I agree thinkers lack feedback: the resistance of the media

This is how I do my ideageneration too.

I always have a thousand ideas in my head, and thinks about them in the shower, before I go to bed, etc. The good ones will tend to stay in my head and materialise more and more into a workable product and the bad (or just impossible) ones tend to fade away because I don't think about them anymore. The stuff I'm working on now has been an idea in my head for around a year, and I've thought about it every day. The result of this is that when I started coding I knew exactly what to make, and I haven't reimplemented or rethought anything because I know exactly what I want to make, down into almost every detail.

Have you shipped yet? If not, how do you know that your new idea won't be similarly DOA, and by waiting you've just pushed back time without finding a product that will work? After all, you thought you had it right before.

Exactly. It would be nice to see a product before declaring victory.

I agree. I had an idea about 3-4 months ago to create a new service for the local community. I wrote it all down, discussed it with a friend, went back and forth, then for awhile it was dead, just a big document sitting there.

I came back to it about a month later and re-evaluated many things, and thought of newer, more clever ways to do certain things

Then I came back to it again about 2 weeks later and finally wrote out my "concrete" plan for Goal #1 and what I want done before moving onto the next phase.

As of writing, Phase #1 is almost in completion. Basically, just like your story, letting the idea sit for awhile gives you time to think it over, see how you can do things different, and get feedback so I think it's pretty valuable in some cases

I've had an idea for a particular product for the US market for something like 10 years... I am continually amazed that no one else has provided it, as many people in Europe love it. Requires a lot of capital, and I'd need to be in the US to pursue it... we'll see.

Is it a train?

The Amero :-O

Heh! No, not that much capital, and I think americans are actually fairly ambivalent about trains (although IIRC, Warren Buffet says he's been investing in them).

It's a food item(s). If anyone's that curious, write me and I'll tell you about it. I guess for me 'lot of capital' is pretty much anything outside the software industry, not 'lot of capital' in more objective terms. I have no idea if it'd be realistic for me to attempt to do something with it, but I know people would like it, with a certainty that I've never had with any other product, which is why it amazes me that no one else has done this particular thing, as there are plenty of established players in the space.

Interesting, my experience is the opposite. When I have an idea, I try to make mockups or crude specs as soon as a I can, and have some sort of basic prototype within a week or two.

Just like you use feedback from blogs to separate the good ideas from the bad, I usually show a few friends my prototype. I have abandoned several projects at the prototype stage, but that's more a question of "Is this something I want to commit a lot of time to?" rather than "Is this a decent idea?".

I always make half a dozen prototypes of the challenges involved in a project before embarking on the actual version. And often I don't even know whether that actual version is the actual version I'll continue with; I just get a feeling at some point that I've got it right.

I sincerely hope all my competitors follow your advice.

Procrastination and darwinism. Those ideas that you actually start on. And then out of those, the ones that you build momentum on, over time.

Funny, this is not my experience.

Whenever I have an idea, I want to act upon it immediately. And then continue to work on it. Sure, I will need occasional breaks, but this is what I think happens...

I find it a little easier to think about an idea when I have something sketched out on paper. I find it a lot easier when I have a prototype, no matter how limited. Both the processes of getting it on paper and getting it on-line clarify my thinking much more than just thinking about it.

I often have to crumple up a lot of paper and scrap a lot of code, but the paper and the code are not what's important. It's what I thought about while I did them that has advanced my thinking about the idea.

This is an interesting counter-point to the "do something, anything -- right now" school of thought.

I think "good ideas", whatever that term means, motivates people to get into the arena. You need something that you feel makes sese with the world. Once you're in the arena, however, it's the flexibility and adaptation that matters. (Fair warning: I'm blowing smoke here, as all I've done is struggle these last few years)

There are two things that I have noticed. First, no matter what your idea or concept, once you put enough work into it you tend to get motivated. So motivation can come later, not at the beginning or a project. Second, really good concepts exist whether you work on them or not. I know -- I've had a couple of really good concepts I've worked on which didn't work out. My execution ability lacked. But the concept didn't just dissapear -- heck no. Some other groups with a lot more execution ability took them and ran with them. (and made a lot of money)

This leads me to believe that really good concepts are like races. Once you "get it", be assured that a dozen or more other people have it also. So you're in a race. I say take all the time you want finding something you feel has magic, but once you got it, run like heck as fast as you can, because time is running out.

I'm in a mode currently where I'm consulting and saving for a few months to run as a startup for a year or so. In the last couple of days I had one of those "ah-ha" moments that occur to me every few years or so. Quite frankly, it scares the crap out of me -- I'm not ready, it's bad timing, I don't have a team in place, etc. But once the idea clicks, the clock starts ticking.

BTW -- anybody interesteed in doing some P2P-type startup work and looking for a team, drop me a line.

EDIT: And I'm not actually an "idea" person. By good idea in this post, I mean a general fuzzy concept that maximizes dozens of criteria simultaneously: marketing, money, deployment, etc. It's an area of interest, perhaps a slogan. But not a concrete thing. You get the concrete thing by executing the concept in the real world, not by imagining it.

Sometimes, ideas improve in the back of your mind, or emerge in a new form when triggered by new external stimulus.

But other times, they rot, or become an unhealthy source of false comfort with inaction. This show from ZeFrank -- when he answers questions a bit of the way in -- really nails the danger:

http://www.zefrank.com/theshow/archives/2006/07/071106.html

For example, he observes sarcastically:

"If you don't wanna run out of ideas the best thing to do is not to execute them. You can tell yourself that you don't have the time or resources to do 'em right…No matter how bad things get, at least you have those good ideas that you'll get to later"

Reply on news.ycombinator.com