I love the idea of a co-op/collective. Kinda of curious as to how it would work in practice. The big problem I think would be who "fronts" for the non-dev/design aspects of projects and kinda herds the cats, handles capacity.
But def interested in being included in investigating whether it's viable. Sounds kinda cool (also, I get to work from thailand, right?... =] ). ciao ! Daryl. On Fri, Feb 24, 2012 at 3:03 AM, Dave McPherson <[email protected]> wrote: > I agree with Mikel here. > > The ability to pass off possible work to a group of individuals, that have > a range of skills and abilities, that are trustworthy is great. There are > lots of ex-clients, and friends of ex-clients that constantly pass me work, > that I have to pass up. > > It's something I think non-tech folk would get. A co-op, of sorts. Like > where you get fish. Only a web site. Kinda. Ha. > > But, on the negative side. Like all committees it's could get thrown into > the "tomorrow I'll do that" basket. Time is a difficult thing, when you're > already juggling multiple jobs, a wife and kid (like me). > > Cheers > --Dave > > On Fri, Feb 24, 2012 at 12:46 PM, Mikel Lindsaar <[email protected]>wrote: > >> This is an interesting idea, and I am saying that while heading up >> http://reInteractive.net/ which you could think is encouraging >> competition. >> >> From my point of view, I get projects coming in the door all the time, >> which are under our minimum budget cut off. Some want a brochure site, >> others want a dev person who can do ongoing work for them. There are a lot >> of these people out there. Just yesterday we turned down a job for a >> client that was in the $20-30k range. This would be pretty good for a full >> time freelancer to do. Would have taken them 2-3 months to get done >> depending on how good they were and probably has some ongoing work for them. >> >> But for us as a development shop, it was not worth taking the job. >> Because we would not be able to deliver everything we do and sets us apart >> from a freelancer for that price. >> >> Having someone or some site I could refer these clients to and I has a >> fairly high confidence that they would get looked after would be good. It >> would also provide a way for me to tell clients I can't help them, but they >> can get help from this team. >> >> But I think trying to formalise the structure would be hard. If you have >> it as a non-profit business, then people have to be on staff to handle >> sales enquiries, match developers with clients, public liability >> insurance, professional indemnity insurance, etc, etc, etc, and that ends >> up looking like a development shop :) >> >> Anyway, that is my two cents worth. >> >> Mikel >> >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. >> >> > > > -- > David McPherson > Ph: 0404 071 385 > email: [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
