This analogy and article are perhaps the best I've heard on the subject because its a metaphor that the ideas people in my life can actually understand.
The metaphor doesn't fret about engineering time, or how simple programming might look but how hard it really is. Ideas people can't relate to those rebuttals anyway.
Instead it brings a very concrete example that almost all humans can understand right away. You want to understand the difference execution makes in an idea? There's a difference between a 9 dollar steak and a 200 dollar steak and its not just the meat, and lots of people understand that. And so I'm going to forward this to a certain ten people in my life.
And a TED Talk comparing the use of patents and trademarks in the fashion industry to software. http://www.ted.com/talks/johanna_blakley_lessons_from_fashio...
Both are quite insightful, and I think you'll enjoy them.
Wikipedia's version, "Some travellers come to a village, carrying nothing more than an empty cooking pot. Upon their arrival, the villagers are unwilling to share any of their food stores with the hungry travellers. Then the travellers go to a stream and fill the pot with water, drop a large stone in it, and place it over a fire. One of the villagers becomes curious and asks what they are doing. The travellers answer that they are making "stone soup", which tastes wonderful, although it still needs a little bit of garnish to improve the flavour, which they are missing. The villager does not mind parting with a few carrots to help them out, so that gets added to the soup. Another villager walks by, inquiring about the pot, and the travellers again mention their stone soup which has not reached its full potential yet. The villager hands them a little bit of seasoning to help them out. More and more villagers walk by, each adding another ingredient. Finally, a delicious and nourishing pot of soup is enjoyed by all."
Sure, it sucks when you have to deal with a fop-cum-restauranteur trying to convince you to sell blah. But you need to listen to the ideas anyway, to hear what people are wanting, or your cuisine turns stale. You need to keep up with the trends of what the customers want to eat, or you end up as a has-been, with a restaurant the does business to the people who never got in when it was the hot thing, slowly rotting to oblivion as eventually everyone who cares or cared has been there, or decided to just resign themselves to never having the experience.
It's simple really, if you're not cooking, cleaning, waiting, providing the building, providing money, marketing or anything BUT providing ideas, you shouldn't be surprised if people find your ideas worthless.
I mostly develop recipes through trial and error, or at the very least the existing knowledge from my cooking skills. The idea that someone who doesn't cook could come up with a good recipe is somewhat absurd.
Recipes which are created by people without any experience may sound good (a good idea), but are actually pretty bad; e.g. the bacon explosion.
That's one bit of advice. The other advice, if given to someone who can afford the change, is to take a job as a pantry chef in a small cafe and work your way up.
He's telling you to get a job.
He's not telling you to get a job doing something else, though he would be cool with that.