Rentacoder lessons - I am a picky coder
after successfully completing my 3rd project on RAC, i learned some lessons. successful project determined by how picky i am. so far i only bid if i really really confident that i am 200% capable of completing the project. Looking at the bid request posts is not always sufficient to judge whether i’m able to complete it or not. I found that the discussion with buyer is the most important as sometimes there are several things still unclear in the bid request. also, during these discussions i will get to know buyer more. i like buyers that list down many points of requirements directly related to project technical aspects, not the things like
I want to have a clone of http://xxxxxxxx.org/, …….
- I don’t want it to be just like flickr, …., but not limited to Riya, Zoomr. 23hq. photopucker, picasa
- The clone must be full engergy, dynamic, sharp, vibrant and similar to http://rrrrrrrrr.com/
it’s most uncreative way to define an uncreative project, and it’s dumb to bid on such project, it’s not for me, however attractive the reward is ;-), my advice, stay away from this kind of buyer/project. i personally avoid such projects since the first time, because i don’t like to clone an application, i only like to code! freshly new code with fresh creative ideas behind it.
ok, here are lessons i learned so far:
- focus on project aspecs
i learned that to successfully win the bid, one must focus on the particular project aspects, provides deep understanding on project requirements and goals by giving sample codes, throwing relevant questions, and suggesting better solution. if the buyer do not response positively on the suggestions, forget it. it won’t work for me. i don’t like to work with people that are not open minded. - wrong category = bad project for me
i never bid on project that are put in the wrong category. RAC defined a very comprehensive catagory for the projects, many aspects are covers by this category system. but still many buyers put their projects in the wrong one. this is either intentionally to defeat filtering system set by coders (i really hate this one), and unintentionally (i rather hate this one) simply because they do not understand what the really want. - so so ranks is not for me
i always spent sometime to have a look on buyer’s history, one of details important to me is how he/she ranked coders that worked for them. if more than 2 below 9.8 points given, i will drop it at once. since i’m developing my rank, i need to find buyers that are generous enough in giving a rank to coders, i just don’t want to drop from 10, i always (and always will) work very hard for it and i deserve it! big exception will be given to fresh buyers. they deserve to be given a change to prove they are generous or not ;-), and sure i take a big risk, but, old time buyers also take a big risk when they pick coders with no onsite experience. nevertheless, i still have change to judge the buyers during pre acceptance discussion. - no communication break down please! and more tea and cookies would be nice also…
last thing (so far) is, don’t be lazy updating buyer! keep communication going everyday during the project. provide small application just to prove your points if necessary. i did several sample programs besides the main projects, just to test the ideas and requirements are realistic or not and in the end will contribute significant values or not to the project. then discuss it in depth with the buyer. so, it’s important to have an open minded buyer! my last project end up almost 4 weeks (instead of initially set 2 weeks), but most of the times are spending into deep discussions on how to produce better solution for the project itself (and creating sample programs). i’m lucky because this particular buyer generously grant 2 more weeks extension. both of us very satisfied with the end result of this project, and begin talking of possibility doing the phase of the project together ;-),
so far i manage to keep my rank at full 30 from 3 projects, it’s great, but not as thrilling as the feeling on completing my first project ;-),
