Mechanical Turk, Visual Studio Edition

Amazon recently introduced Mechanical Turk, a site that automates the process of taking work that only humans can do well (like judge the quality of a photograph) and paying users to do that work.  Anyone can log in, spend some time ranking photographs and make a few bucks.

I want this as a Visual Studio plugin.  Here’s how it would work.

I’m a typical coder, which means I’m lazy.  I sit down to write an app and part of what this app does is read settings from a config file.  This is boring work, so typically the first time through, I fudge it:

   // TODO: Move this into a config file
   numThreads = 4;
   serverName = “bob.com”;

The act of reading this info from a config file is perfect Mechanical Turk work.  It’s work that any developer with basic skills can do, but it’s just typing.  If I could pay someone $1 to do this work for me, I’d do it.  Here’s how:

First off, you select the code you want to replace, and select Submit to Turk from the menu:

 Now you have to answer some basic questions.  What do you want the new code to do, and how much are you willing to pay for it:

I submit this.  Now as I continue typing, somewhere out there a Turk takes this work unit and does it.  In a few minutes, I receive this notifiation:

Cool!  View Now…

There it is!  I’ve given a coder somewhere $1.00 (plus a 15% tip) for saving me a bit of time.  The workflow being integrated into Visual Studio is what makes it worthwhile - if it was email based or something like that, the overhead would be more work than the time you were saving.

Now, someone go implement this!  Any volunteers?

 

2 Responses to “Mechanical Turk, Visual Studio Edition”

  1. Ben Says:

    This is an absolutly fantastic idea! :)

    Sort of like Rentacoder.com, but built into the IDE. I like your thinking!

    Heres the only problem, what happens when the coder submits the work, then the buyer looks at the source code and Rejects, but secretly uses the code…

  2. Jake Says:

    Good point. How about the payment money be immediately kept in a transactional “escrow”, and the code be presented to the buyer as well open as a peer reviewed. If the review committee approves the code (by electronic vote), the majority (95%?) of the $$$ gets released to the coder, and the rest $$$ gets divided up to the reviewers for their help. If not, the reviewers still get paid, but the remainder goes back to the buyer.

    There could also be an open rating system similar to eBay so that potential swindlers won’t get repeat business.

Leave a Reply