[duopixel]

I'm always amused at the "why don't you try building it yourself" response developers give when they're asked this kind of question. The amount of knowledge you need to execute an idea is staggering. Deep down they know there's a 99.9% chance the guy will fail.

It's as if a person went up to an architect and asked him to build him a hotel with promises of sharing the future revenue stream. Architect responds "I can't, but if you don't have money you could try building it yourself".

There's no easy answer for the penniless idea guy. Perhaps stating (in a very polite way) that—as the biz guy—he should work on his own net worth before generating it for others.

[SwellJoe]

I've seen people learn to code in order to build their ideas. It's even occasionally turned out OK.

I've also seen people learn to build in order to build their own gazebo, deck, and even a log cabin. It's not a hotel, but it is a useful piece of construction that a person with no architecture eduction can build with only a moderate amount of knowledge and experience. Some development projects are the equivalent of a deck or gazebo: A weekend project for someone experienced, and a two week learning process for someone who's never lifted a hammer (or opened a text editor).

I don't think it's terrible advice for an "idea guy" that doesn't have money. That's not to say it'll be a success. It almost certainly won't. If they're competing with experienced developers, they'll probably lose in the market, but they'll learn more about the value of developer time, and they'll learn how to better interact with developers because of that understanding. Maybe their next project will be more realistic, and they'll figure out how to fairly compensate a developer for their time.

That said, I think your last sentence is very astute. Maybe a self-proclaimed biz guy ought to prove himself by getting money lined up first, either by earning it, or convincing people to invest in him.

[jtbigwoo]

Just creating and publishing a simple app or proof of concept can make a huge difference in generating interest from possible partners.

Most biz guys make the following offer: "I have an idea; I need you to implement it." Imagine if he could say this: "I have a prototype that I've been working on, but it's pretty amateurish; I need you to make it professional." I know which one I would take seriously.

[mgkimsal]

Or even "I paid someone to do some mockups and/or a small prototype, but I need someone to make it really work properly". That would indicate they'd gone beyond the 'idea' stage in to concrete action, and aren't afraid to put up a bit of cash to get started.

[owenmarshall]

>Maybe a self-proclaimed biz guy ought to prove himself by getting money lined up first, either by earning it, or convincing people to invest in him.

That's the difference between an "ideas man" and an entrepreneur. And it's the easiest way to successfully differentiate when someone approaches you with an idea.

A real entrepreneur understands that ideas are worthless; only implementations have any value. Thus, they will be ready and willing to pay you (gasp!) for your time.

I, like almost every programmer out there, I'd imagine, have been approached multiple times by people with great ideas. What quickly distinguishes the serious partners is asking them what they can bring -- not will bring, but can bring -- to the partnership. A true partner will show you a rough mockup of their ideas, market research, and a stack of cash they pulled together. The ideas guy will tell you that the idea alone is worth your time.

[paulnelligan]

that's exactly what I did, I decided that nobody was going to build my product but me, so I taught myself Rails, went to developer meetups, and 3 years later I have a nearly finished product and am working full time as a Rails developer ... True it's taken me a long time to learn the skills necessary to build, but it's been a worthwhile journey!

[josephcooney]

That's pretty inspiring. Congratulations. Out of curiosity, was your idea in a domain that you had experience with in your pre-developer life?

[paulnelligan]

yes, most definitely ... I saw the need for this, and amazingly 3 years later, still do ... whether or not the endeavour is successful, the benefits of DIY'ing it far outweigh the benefits of just paying someone else to do it ...

[mnutt]

Even if you can't perfectly execute on your idea, the fact that you've built something yourself probably means that a) you care enough about the idea that you want to see it built one way or another, and b) you've thought through how the product will work sufficiently to build something. I would guess that most people who come to developers with ideas haven't actually thought the product though very much.

If you make a prototype that shows promise and show it to me, I'm more likely to start thinking "this is really cool, how can I make this awesome?" than "this person wants me to build something for them for free".