3 ms·

There’s no misconception. Until I commented, there was no disclaimer stating that the code was not ready for production use and was for research purposes only.

There’s no misconception. Until I commented, there was no disclaimer stating that the code was not ready for production use and was for research purposes only. Very few people are qualified to review and critique this type of codebase so it’s dangerous to market a repository backed by multiples professors and PhDs as “it does X, Y, and Z” It would be great to live in a world where people did a serious review of projects before downloading them but that’s not the reality we live in. OP didn’t provide any context either that this was focused on reviewing the paper and concepts in it so I think what you mean is that “you think people should focus on the paper” but “we focused on the code”, that’s not a misconception, it’s a lack of clarity by both OP and the project website about what’s important. If the code was irrelevant, it should be removed from the website so that the audience could focus solely on the paper.

javert 7y ago
> it’s a lack of clarity by both OP and the project website about what’s important As a former academic, I can immediately spot this website as an academic paper with a bit of code on the side. Academics do this kind of thing constantly because they get kudos for it in academic circles. Yes, there is a lack of clarity (if you are not an academic). That's why I pointed this out for what it is. > If the code was irrelevant, it should be removed from the website so that the audience could focus solely on the paper. I mean, you're not wrong. But then they wouldn't get as many kudos from their academic buddies.
- dkoston 7y ago
  I agree that this stuff is common place and I definitely understand that in today’s world of noise that you have to market yourself and your papers to get attention. I was glad to see them add the disclaimer as hopefully it’ll turn away people who see “hey, here’s this secret management project made by a bunch of professors and PhDs, I should use it because they are super qualified”. My goal was to provide feedback to the students about how people evaluate code “in the real world”. It’s not helpful for them to be applauded for “sub par” code but you raise a good point that it can seem harsh to not provide feedback on the “meat of the project” which is their paper and research.

javert 7y ago

> it’s a lack of clarity by both OP and the project website about what’s important As a former academic, I can immediately spot this website as an academic paper with a bit of code on the side. Academics do this kind of thing constantly because they get kudos for it in academic circles. Yes, there is a lack of clarity (if you are not an academic). That's why I pointed this out for what it is. > If the code was irrelevant, it should be removed from the website so that the audience could focus solely on the paper. I mean, you're not wrong. But then they wouldn't get as many kudos from their academic buddies.

dkoston 7y ago
I agree that this stuff is common place and I definitely understand that in today’s world of noise that you have to market yourself and your papers to get attention. I was glad to see them add the disclaimer as hopefully it’ll turn away people who see “hey, here’s this secret management project made by a bunch of professors and PhDs, I should use it because they are super qualified”. My goal was to provide feedback to the students about how people evaluate code “in the real world”. It’s not helpful for them to be applauded for “sub par” code but you raise a good point that it can seem harsh to not provide feedback on the “meat of the project” which is their paper and research.