Re:Differences between the word2vec paper and its implementa...
by itronitron on Tuesday June 04, 2019 @05:52AM
(#20093466)
In my opinion, a paper should describe the contribution in sufficient detail that it can be implemented by someone with similar expertise. I believe that would foster greater innovation as people would necessarily have greater familiarity with all of the details, and they would better see why the thing works or doesn't.
Re:Differences between the word2vec paper and its implementa...
by raverbashing on Tuesday June 04, 2019 @02:31AM
(#20092454)
> Scientist code isn't software engineering code (and software engineering code is very often worthy of criticism)
Absolutely correct, and not in a good way
Though to be fair, people doing research have other interests besides maintainable code (though half or more of the annoyances will probably come and bite them later)
Re:Differences between the word2vec paper and its implementa...
by curl_e on Tuesday June 04, 2019 @01:54PM
(#20097506)
The good news is people are trying to address this. Starting in the UK there is a movement for Research Software Engineering https://rse.ac.uk/ and happening right now is the German RSE conference https://www.de-rse.org/en/conf2019/
Re:Differences between the word2vec paper and its implementa...
by dTal on Tuesday June 04, 2019 @04:05AM
(#20092941)
>It's just good news when you can find source code at all instead of just being told vague things about something the author did.
This is extremely common, and I don't see why it should be allowed. I could easily write a paper claiming some kind of interesting result, fake a few "ground truth vs my algorithm" pairs, and talk a bit of mathy-sounding piffle about what it does - and it would be indistinguishable from many papers I have read.
In my opinion - provide runnable source, or what you have isn't a paper, it's a boast.
It's just good news when you can find source code at all instead of just being told vague things about something the author did.