Craig is spot on.

To add a couple more things. It's a great idea, something like the romantic
vision of building a utopian community, but, alas, things just don't work
that way.

Consider it from the client's perspective:

* if it's a major project, which entity (amongst the pool of freelancers)
will be there in a year for phase 2? If it's not the same collection of
coders (the group might change constantly) why should the client pay for a
new set of eyes to learn the codenbase? Who has corporate insurance (for
decent budgets, this is normally mandatory)?

* beyond that, there's the hard fact that finding good coders to work with
is hard, and often takes repeated efforts. That's why people who choose to
build company's together have a further reason to make sure it works on a
coding basis - they want to see profit and success in the longterm for what
they build together. If it's a short term collection of coders (perhaps
some with rockstar attitudes), you might find the cooperation a little bit
painful for the team and unproductive for the client.

I don't want to be overly negative about the thought. The thought has often
occurred to me as I've freelanced (I've been remote working since 2006). I
ended up forming my own private company in the end, for many of the reasons
above. As soon as that happens, the work distribution becomes uneven
between long-termers and short-termers.

Anyway, cheers,
Nicholas

--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rails-oceania/-/2sxHWW_ucJwJ.
To post to this group, send email to rails-oceania@xxxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
rails-oceania+unsubscribe@xxxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.