aciddose wrote:Why do you need a programmer at all? You sound like you can keep 100% of the idea and implement it yourself.
For different reasons, but mainly, because I have chosen to focus on web technologies. Its enough for me to learn about Software Engineering in general, and web technologies like PHP, JS, different DBs, HTML, CSS etc. I do also try to develop web related businesses. I think its best to focus on that for quite some time, and not try to learn C++, DSP etc. also.
aciddose wrote: Otherwise, exactly how much is this worth? The idea vs. a working implementation of that idea?
Your idea is worthless as it is now. It is only worth something once it is implemented.
Well this might turn into a endless philosophical debate..
In the end the market decides values, or simply what people agree upon. In this specific case its a possible partnership so the most important thing is that both parties think the agreement is "fair". Its kinda impossible to say exactly "what is objectively right", but if both consider it to be "fair" it is at least "ok".
And, also, if I have an idea and the programmer wants to implement it does probably mean that he does consider my idea greater then his own.. else why would he care about implementing mine, and not rather his own ideas? And since it is mine and I give it away it would be obvious that I should get something in return.
What that "something in return" is.. that is arguable of cause, but it could depend on the greatness of the idea. If its just a little thing then maybe the right thing would be that I get the implementation/end product for free (this is the minimum fair return I guess), but if the idea is expected to make huge profits if implemented right, then I say its fair that I should have a share of equity/profit that relates to those expectations.
aciddose wrote: You probably have the scale of equity tilted a little bit too far toward yourself and your idea.
Why do you think so? I dont think so..
maybe we would end up disagreeing.. maybe not.. idk..
aciddose wrote: ..your idea.
What I answered so far was under the assumption of "an idea". In my cases its not "an idea".. it is "an architecture" (or actually many). So its more one (or more) main idea, with many sub-ideas and concepts, into a coherent system with many parts and relations. This means brainstorming, decision making, descriptions, drawing, designs.. etc. That is actual work too, much more than just "an idea".
I think the most easy agreement would be equity based on actual work. If the description of the system took 1 week of work do design, and the implementation took 49 weeks, equity split would be 2% to the "idea guy" and 98% to the programmer.