It is also typically the case that about 2/3 of the project consists of moving the code from "working" to "usable". That involves writing up examples, wiki pages and ironing out strangeness in how the program is invoked or how the output might be consumed.
On Mon, Mar 22, 2010 at 12:52 PM, Robin Anil <robin.a...@gmail.com> wrote: > But from the looks of it what I would suggest you is to > target a somewhat lower and practical proposal. Trust me converting these > algorithms to map/reduce is not as easy as it sounds and most of the time > you would spend in debugging your code. >
