I don't think it would be hugely useful, since each piece of code exists in a unique ecosystem. Think about libraries, dependencies, OS versions, etc. Therefore no guarantees would be possible, therefore there would be arguments over paying-up.
However... If you extended it to defined "micro-projects", perhaps that might work better. This would require some basic specs from those requesting the work. What version of X, what OS exactly, etc etc. Plus a reasonable description of what success looks like (and what failure looks like).
Not sure you could achieve that.
Classic tension: too lightweight and it won't work; but adding features/requirements until it does work will make the process too heavyweight to be appealing.
Solve that tension and you have a product. Not sure you'd make any money from it though :)
Comments
I don't think it would be hugely useful, since each piece of code exists in a unique ecosystem. Think about libraries, dependencies, OS versions, etc. Therefore no guarantees would be possible, therefore there would be arguments over paying-up.
However... If you extended it to defined "micro-projects", perhaps that might work better. This would require some basic specs from those requesting the work. What version of X, what OS exactly, etc etc. Plus a reasonable description of what success looks like (and what failure looks like).
Not sure you could achieve that.
Classic tension: too lightweight and it won't work; but adding features/requirements until it does work will make the process too heavyweight to be appealing.
Solve that tension and you have a product. Not sure you'd make any money from it though :)