Live data from Hacker News

Ask HN: Co-Ops for Developers?

news.ycombinator.com

21–23 of 23 posts

Re: Ask HN: Co-Ops for Developers?

#21
post #17
post #13

Earlier quoted context omitted.

My thoughts about a collective have included a bidding system. For each project, the coordinating team identify the work units. For each work unit, the collective's members may submit a bid comprising of: * time available to work on project (start date, commitment, etc.) * time estimates * profit-sharing margin The project coordinators choose a best fit. All assets created by the collective are added to a common pool…

That's an awesome idea, using a kind of market to decide the price/profit. You need some kind of reputation to make this work, you don't want any fool bidding and then not doing the work.

It's a design I've been tinkering with for while and have a bunch of notes about. Reputation would be handled by a transparent history of all projects worked on.

The profit-sharing design does not prevent collusion. E.g., if there are a glut of programmers and a shortage of artists in the collective, then two may collude to submit and share a low programmer bid and a high artist bid (and vice versa on another project).

Collectives are hard and are subject to many problems that the free market does not suffer.

Re: Ask HN: Co-Ops for Developers?

#22
post #16
post #7

Earlier quoted context omitted.

Do you mean based on number of lines of code?!

Why is this downvoted? "License an open source formula based on the value of short/long contributions" sounds like LOC to me. Dividing income fairly is the core issue. Solve that and the rest is easy. The problem is that this is very hard.

I forget who it was, but there was a car factory that worked like this:

Groups no larger than 6, reporting to higher groups of 6, up to how many levels you need.

Within the groups of 6, they work out themselves who gets paid what, completely transparently.

The amount everyone gets paid is posted publicly. It worked, because people set the rates fairly in the groups.

If your going to do something slightly anarchistic like be by developers for developers you might as well go the whole hog.

Oh, also make sure the whole organisation isn't bigger than 150 at any time - staying within the dunbar number seems like a great idea.

Post reply on HN