> First we needed a mobile app to administer the server so we hired an experienced mobile developer through guru.com. His credentials were great but maybe it should have been a tip-off when, right after we made the first payment, the developer moved from Europe to India... We were naive. The original development estimate was exceeded in the first week and we were up to more than 8X by the time we pulled the plug. Still the developer kept trying to charge us, eventually sending the project to arbitration, which we won.
This smacks of the client not knowing how to use a developer. Meaning: I can imagine they made a simple (probably incomplete) scope or product definition document, didn't realize where the complexity actually lay, found someone cheap, and then realized that no one had the ability to actually shepherd the project to completion. They knew nothing about their developer -- and she or he knew nothing about them. And they weren't paying that much, really. So it wasn't a huge priority in the developer's life. And maybe the dev was young or just kind of between things and something more important came up or whatever. It actually takes some thoughtfulness to be a professional freelancer. Can be harder sometimes than it looks.
Cheap overseas developer talent is fine. But. There's also a huge value to finding people who you can sit down with and talk to. Meet. Get to know a bit. Professional freelancers will absolutely help naive clients identify and avoid pitfalls from the start. We (professional freelancers) have already fallen into them all and generally have the scars and callouses to know what it really takes to produce good software in a freelance environment. Professionals know how much time and effort it actually takes to do things. They'll tell you if your "I need a Facebook clone next week" project has any chance of success. They'll help you with design and they'll help you understand the trade-offs between money, time, and functionality that all software projects must make.
Sounds like none of that happened here.
Anyway. This just touched a nerve for me. Maybe I'm totally off base.
This smacks of the client not knowing how to use a developer. Meaning: I can imagine they made a simple (probably incomplete) scope or product definition document, didn't realize where the complexity actually lay, found someone cheap, and then realized that no one had the ability to actually shepherd the project to completion. They knew nothing about their developer -- and she or he knew nothing about them. And they weren't paying that much, really. So it wasn't a huge priority in the developer's life. And maybe the dev was young or just kind of between things and something more important came up or whatever. It actually takes some thoughtfulness to be a professional freelancer. Can be harder sometimes than it looks.
Cheap overseas developer talent is fine. But. There's also a huge value to finding people who you can sit down with and talk to. Meet. Get to know a bit. Professional freelancers will absolutely help naive clients identify and avoid pitfalls from the start. We (professional freelancers) have already fallen into them all and generally have the scars and callouses to know what it really takes to produce good software in a freelance environment. Professionals know how much time and effort it actually takes to do things. They'll tell you if your "I need a Facebook clone next week" project has any chance of success. They'll help you with design and they'll help you understand the trade-offs between money, time, and functionality that all software projects must make.
Sounds like none of that happened here.
Anyway. This just touched a nerve for me. Maybe I'm totally off base.