Idea Guy Looking for Developer
bubblefoundry.com
Idea Guy Looking for Developer
1–10 of 109 posts
Re: Idea Guy Looking for Developer
#2"They both think that less skill is required (so the programmer doesn’t deserve much compensation) and that less time is required (effectively creating a very low hourly rate for the programmer, given the flat rates that are often proposed)."
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.
Re: Idea Guy Looking for Developer
#3"They both think that less skill is required (so the programmer doesn’t deserve much compensation) and that less time is required (effectively creating a very low hourly rate for the programmer, given the flat rates that are often proposed)." 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 himsel…
> 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?
Programming can be a hard-earned skill that an intelligent idea guy can acquire. No false dilemma required.
Re: Idea Guy Looking for Developer
#4This is an issue that comes up over and over. The real problem is a mismatch of supply and demand: there are lots of ideas out there, and not enough developer hours to bring them all to fruition, so a guy with an idea will need to offer more than just the idea if he wants to attract developer time. Someone who fails to understand this problem probably shouldn't be trying to start a business.
Re: Idea Guy Looking for Developer
#5This article talks a lot about money and time but doesn't mention the simple fact that some developers (or is it only me) won't want to work with certain people.
As a developer I'm not going to work closely with someone I don't like.
I guess my message would be: Sometimes developers just aren't into you and your ideas. Perhaps you need to try and understand them more.
Re: Idea Guy Looking for Developer
#6I'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.
Re: Idea Guy Looking for Developer
#7"They both think that less skill is required (so the programmer doesn’t deserve much compensation) and that less time is required (effectively creating a very low hourly rate for the programmer, given the flat rates that are often proposed)." 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 himsel…
The alternative is paying a competitive rate, or splitting equity in a fair way, or both. If an "idea guy" doesn't want to get his hands dirty and doesn't want to pay someone to do the actual work, well...screw that guy. Nobody owes him anything.
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.
Re: Idea Guy Looking for Developer
#8"They both think that less skill is required (so the programmer doesn’t deserve much compensation) and that less time is required (effectively creating a very low hourly rate for the programmer, given the flat rates that are often proposed)." 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 himsel…
It's not simply that programming itself is difficult, it's that ideas conceived without knowledge or consideration of the technical implications are frequently more difficult to implement than a non-technical person realizes.
Re: Idea Guy Looking for Developer
#9"They both think that less skill is required (so the programmer doesn’t deserve much compensation) and that less time is required (effectively creating a very low hourly rate for the programmer, given the flat rates that are often proposed)." 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 himsel…
It's a hard-earned skill and in trying to do it himself, the idea guy will learn to appreciate that fact.
Re: Idea Guy Looking for Developer
#10I'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…
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.