3/31/13
3/30/13
why no applicants?
hm.. I've posted a number of humanscripts which are not getting any applicants. I wonder why. One possibility is that I haven't designated any "skills" for them, and maybe people search by skill. One reason I haven't designated any skills is that the oDesk API doesn't currently support that.. I'll try adding skills manually, and if that helps, I'll need to talk to someone about adding skill support to the API.
february-fire first humanscript
finally! I'm posting a humanscript for february-fire — this was the secret goal all along with taking on that project. Here is the humanscript in github issue form: https://github.com/dglittle/february-fire/issues/1
ok, posted it.. I put it as a $50 job, since it involves comprehending my code a little bit. we'll see if we get any takers..
ok, posted it.. I put it as a $50 job, since it involves comprehending my code a little bit. we'll see if we get any takers..
throbber
I created this issue: https://github.com/dglittle/misc/issues/1
A friend came along and did it: https://github.com/alltom/misc/blob/gh-pages/throbber.html
Here's a running version: http://dglittle.github.com/misc/throbber.html
I'm not quite sure how he found out about it.
I sent him a link to the job posting on oDesk so he could apply, and I could pay him.
Done, and done :)
Next, I want to use that throbber in nodesk.. here's the issue: https://github.com/dglittle/nodesk/issues/2
A friend came along and did it: https://github.com/alltom/misc/blob/gh-pages/throbber.html
Here's a running version: http://dglittle.github.com/misc/throbber.html
I'm not quite sure how he found out about it.
I sent him a link to the job posting on oDesk so he could apply, and I could pay him.
Done, and done :)
Next, I want to use that throbber in nodesk.. here's the issue: https://github.com/dglittle/nodesk/issues/2
a couple humanscript side projects
I had a couple of ideas that I want to humanscript. One is an advanced-chess server. The other is an add-on to the yabla language learning video player — I want it to show translations for each word directly beneath each word.
For the advanced-chess project, I created this issue: https://github.com/dglittle/advanced-chess/issues/1 , which has someone create a chess board using unicode characters. The next step will be to draw a chess board given a FEN string.
For the yabla project, I created this issue: https://github.com/dglittle/yabla-extension/issues/1 , which has someone create a starting point for a chrome extension that can interface with yabla. The next step will be to have it augment the way the transcription is shown.
I posted both of these issues on oDesk using nodesk.
For the advanced-chess project, I created this issue: https://github.com/dglittle/advanced-chess/issues/1 , which has someone create a chess board using unicode characters. The next step will be to draw a chess board given a FEN string.
For the yabla project, I created this issue: https://github.com/dglittle/yabla-extension/issues/1 , which has someone create a starting point for a chrome extension that can interface with yabla. The next step will be to have it augment the way the transcription is shown.
I posted both of these issues on oDesk using nodesk.
3/29/13
more humanscript work notes
I just created an issue here: https://github.com/dglittle/misc/issues/1
I created a super simple job — maybe too simple. It just says "github issue: create a throbber", and the task description just has a link to the github issue. We'll see how that goes.
Now to post the other one.. done. Ok, let's see how those turn out.
update: hm.. I don't give much indication up front about how big the task is — maybe I can just say in the title "about 1 hour". Ok, I edited the titles to include "(about 1 hour of work)".
I created a super simple job — maybe too simple. It just says "github issue: create a throbber", and the task description just has a link to the github issue. We'll see how that goes.
Now to post the other one.. done. Ok, let's see how those turn out.
update: hm.. I don't give much indication up front about how big the task is — maybe I can just say in the title "about 1 hour". Ok, I edited the titles to include "(about 1 hour of work)".
humanscript notes
I posted four humanscripts last night.
Notes:
For one job, I asked someone to write a simple function for creating lorem-ipsum style random text. The person I hired had submitted completed code as part of their cover letter. I should have hired them to add the functionality I needed to an existing open-source lorem-ipsum generator.
For another job, a hired the first applicant who answered my three questions correctly, and they sent me a screenshot for verification this morning — it looked correct.
Two of the humanscripts failed to get any applicants. I need to figure out why. One asks someone to create a simple throbber, and insert it into a larger project. I think I should split that one into two tasks: creating the throbber, and inserting it.
After talking to my friend, I think it will also help to make the jobs into github issues, for better accountability (something for me to put links to from here), and also to provide more context to the workers about the job.
So next steps:
- split the throbber job into two sequential jobs, and post the first one as an issue
- repost the alignment job as an issue
Notes:
For one job, I asked someone to write a simple function for creating lorem-ipsum style random text. The person I hired had submitted completed code as part of their cover letter. I should have hired them to add the functionality I needed to an existing open-source lorem-ipsum generator.
For another job, a hired the first applicant who answered my three questions correctly, and they sent me a screenshot for verification this morning — it looked correct.
Two of the humanscripts failed to get any applicants. I need to figure out why. One asks someone to create a simple throbber, and insert it into a larger project. I think I should split that one into two tasks: creating the throbber, and inserting it.
After talking to my friend, I think it will also help to make the jobs into github issues, for better accountability (something for me to put links to from here), and also to provide more context to the workers about the job.
So next steps:
- split the throbber job into two sequential jobs, and post the first one as an issue
- repost the alignment job as an issue
Subscribe to:
Posts (Atom)