4 ms·

I'm genuinely interested: jeeves weighs in at ~20k loc. at 50 lines of code/day that's a 1 year endeavor. I know there's a lot of research upstream, TAing, writ

I'm genuinely interested: jeeves weighs in at ~20k loc. at 50 lines of code/day that's a 1 year endeavor. I know there's a lot of research upstream, TAing, writing papers, and so on, but 50 loc/day is something very achievable while doing lots of other things. My naive question is why/how does it seem like the final result is way smaller than what I would expect for 7 years of research?

deleted 11y ago
[deleted]
jrowley 11y ago
With normal programming (e.g Python web development) you have a really good idea of what you are building before hand. That's not necessarily the case here. Also it sounds like they did various rewrites at different points.
riyadparvez 11y ago
I am not sure what you are getting at. Are you counting productivity by LOC? To sum-up: - This is not her only project, just the main project - She has taken grad courses, doing a grad course in MIT will easily be more work than average developer do in whole year. - She had to study several research areas before choosing her main project. It is unlike I read the tutorial of currently trending distributed system Apache Spark and now I know everything about state of the art research. It is going through dozens of research papers in that domain, understanding all the concepts, identifying the gap in existing research, figuring out how to fill that gap. - You will fail several times before finding a good approach. The author have mentioned she had tried with Scala first, later switched to Python. - Even the results are good, you have to write the paper which is not trivial, and getting it accepted before getting rejected several times. - Worst case scenarios are also likely. Mid-way in the project you have found out someone else has recently published a paper. Now your work is worth-less because it is already published. Or you have found it there is an obscure paper that also outlined the approach you have taken, now you have lost the novelty factor of your paper. TL;DR: 200 lines of some UI JS code is not same as 200 lines of new deep learning algorithm in TensorFlow.

deleted 11y ago

[deleted]

jrowley 11y ago

With normal programming (e.g Python web development) you have a really good idea of what you are building before hand. That's not necessarily the case here. Also it sounds like they did various rewrites at different points.

riyadparvez 11y ago

I am not sure what you are getting at. Are you counting productivity by LOC? To sum-up: - This is not her only project, just the main project - She has taken grad courses, doing a grad course in MIT will easily be more work than average developer do in whole year. - She had to study several research areas before choosing her main project. It is unlike I read the tutorial of currently trending distributed system Apache Spark and now I know everything about state of the art research. It is going through dozens of research papers in that domain, understanding all the concepts, identifying the gap in existing research, figuring out how to fill that gap. - You will fail several times before finding a good approach. The author have mentioned she had tried with Scala first, later switched to Python. - Even the results are good, you have to write the paper which is not trivial, and getting it accepted before getting rejected several times. - Worst case scenarios are also likely. Mid-way in the project you have found out someone else has recently published a paper. Now your work is worth-less because it is already published. Or you have found it there is an obscure paper that also outlined the approach you have taken, now you have lost the novelty factor of your paper. TL;DR: 200 lines of some UI JS code is not same as 200 lines of new deep learning algorithm in TensorFlow.