It doesn't matter if it is easy or hard...if the idea guy won't do it himself, and he doesn't want to pay someone else to do it, it's not going to get done. And that's as it should be. If idea guy starts learning to code, he might learn enough to know what the work is worth, and will be better equipped to make the deals needed to get the hard parts done by competent developers. He may also gain the respect of actual developers; I wouldn't team up with guys who can't code at least a little.
I thought it was a very polite way to approach the topic. I'd be much more tempted to just say, "The only time I work for free is when it is work I want to do, on my own ideas, and where I own the result. Stop emailing me." But, I'm not renowned for my social graces.
I used to just be an idea guy. Then I realized I should learn to program. I'm not the best developer out there, but in an afternoon I can crank out something in Ruby to see if my general concept/logic works. My code will be sloppy, best practices might not be followed, but I can iterate quickly and see if it actually was a practical idea.
Examples of 'idea guys' not understanding is their lack of familiarity with APIs. They think they can just do everything perhaps imaginable, but really there are limitations. Want to crawl the entire social graph of Twitter? Yea, good luck with that. Even with 20,000 API requests/hr, you'll never catch up. You can't just snapshot it also and see changes every day. But an "idea guy" might think that this would be a great idea. It isn't that the programmers turning them down aren't good enough, but just that some things aren't possible with given APIs and unless you're coming to them with $10M+, Twitter isn't going to change their API for you.
Programming can be a hard-earned skill that an intelligent idea guy can acquire. No false dilemma required.
The intersection is getting larger thanks in part to engineers self-deprecating like this, which is potentially good for innovation and potentially bad for my wallet.
The real advantage in telling the "idea guy" to try to build it themselves comes when they realize that programming is difficult. Sure, they could master it if they were willing to put in the time and effort, but their interests center around the business: sales, investors, etc.
At this point, the idea guy has two choices: either understand that they've got to bring something more than ideas to a partnership, or stubbornly cling to the hope that their idea is enough.
The more people that realize that ideas alone have no value, the better.
I should add that most developers don't seem to have much of this knowledge either. It comes from a rare blend of anticipating customer needs, technical understanding, and general pragmatism. The more projects I work on, the more I come to believe that someone who fills this gap is worth ten times more than both the dude with the 'great idea' and the all star coder.
He's suggesting the idea guy work hard to earn the skill of a programmer, or at least learn enough to know what's hard and what's not.
I find it ironic how he points out that idea guys tend to undervalue the hard work of the programmer and then at the end he suggests that the idea guy should implement it himself.
So which is it? Is programming a hard-earned skill that should be paid well, or is it just so easy that a (presumably non-technical) idea guy can just pick it up and run with it? You're sending mixed messages.