4 ms·
Lessons: 1. Don't hire people without getting to know them first a bit. 2. Don't hire people who cannot give references. 3. Don't expect cheap jobs to come t
by orangethirty 14y ago
Lessons:
1. Don't hire people without getting to know them first a bit.
2. Don't hire people who cannot give references.
3. Don't expect cheap jobs to come through. You pay for what you get.
4. Do hire someone from the monthly HN freelancers thread. Lots of reputable people in there.
5. Don't expect a freelancer to also be a security expert. Some just deliver the system, you need to hire security consultants to make it secure.
6. Do subscribe to codejobs. A newsletter I run where people like you can meet and hire reputable people. Its free. http://eepurl.com/uOdzP http://eepurl.com/uOdzP
7. Rants like these put you in a bad light. Put them on your blog and link here. Posting it directly makes you lose control of the content in case this turns into a PR disaster.
8. Posting the name of the developer is not cool. You are not giving him/her/them a chance to post their side of the story. For all we know you are the scammer.
- mudil 14y agoorangethirty: Thank you for your first 7 points. However, I cannot agree that posting the name of the developer is "not cool". I attached an entire file of my back and forth to support my case. Furthermore, I am complaining about Freelancer.com, and not the developer.
- orangethirty 14y agoMudil, This is not a court. You do not have a need to support your case. By making the name public you are just making yourself look bad. That is why I made point 7. Don't argue. Delete this post while you can. Save yourself the trouble.
- true_religion 14y agoI don't agree. Freelancers who work online are used to having their name out there. It's part and parcel of the reputation systems built by Freelancer.com, Guru, and E-lance. Once work is completed, you get a public review. To me, his main legitimate complaint is that Freelancer.com didn't allow him to leave a review, so he has to turn to taking his story to the wider public. I don't really agree with his story, but he does have a write to name whom he has worked with in the past.
- orangethirty 14y agoSure, though like I said, he is posting his side of the story. This could even be considered as libel by some lawyers. That is why you just don't post stuff like this publicly. The legal risk is too big.
- mootothemax 14y agoThank you for your first 7 points. However, I cannot agree that posting the name of the developer is "not cool". I attached an entire file of my back and forth to support my case. Furthermore, I am complaining about Freelancer.com, and not the developer. Giving another perspective, I also agree that this puts you in a bad light. It's unfair, and it shouldn't do, but if you wanted to work with me, and I saw this post, I would most likely decline. Why? Because it implies there might be drama attached, and no-one wants that in their life, especially when it's such a coders' market right now. As I say: I recognise that this is unfair. There should be a good way to say "stay away from this person - they wronged me!" somehow. This isn't it, though.
- speeder 14y agoorange how you check if the person is reputable or not?
- orangethirty 14y agoSpeeder, I talk with them through email and Skype. That usually gives me a good feel for the person. But that will not work for everybody. And its not 100% effective, because I have been scammed before (by big name startup founders).