I do agree that the advisor should have pushed back lots harder on the methods; it's a weak paper, even as an experience report.
I agree - this seems to be mostly the advisors fault, by the looks of it it's not that the student didn't put a lot of work into it but methodological problems are what advisors are supposed to be there to address; I saw a lot of this back in college, at least with technical papers it's easy to tell what's wrong, with the humanities it's just a complete disaster.
http://www.erlang.org/doc/tutorial/introduction.html http://www.erlang.org/doc/tutorial/nif.html#id64792
The advisors should have encouraged a smaller and more manageable scope with a more thorough methodology where the results would actually be worth something.
You mean it has nothing to do with learning correct methodology or actually doing real research?
That's exactly the attitude emblematic of the portion of academics producing worthless output.
Here is a recent reference: http://www.nature.com/news/psychology-journal-bans-p-values-...
Not a methodological problem?
The article submitted was not peer reviewed, and could very well be bad science, but I think accusations of non-science are not very productive and do not provide feedback in how to do better.
My point was rather that there was so much low quality research they decided to try to filter it by banning a statistical tool. Are you saying the reasons for so much low quality research had nothing to do with methodological problems? Maybe it's not low-quality, since you know it's "subjective"...
> The article submitted was not peer reviewed, and could very well be bad science, but I think accusations of non-science are not very productive and do not provide feedback in how to do better.
You are addressing a point I never made. What I said was(quote): The advisors should have encouraged a smaller and more manageable scope with a more thorough methodology
Because an important part of undergraduate education is in fact learning to be able to tell what good research is. The advisor's aren't really benefiting them by not pointing out methodological problems and letting them do research ">>>>> wherever that may lead them" - because that only encourages methodologically sloppy work in the future.
He rewrites a distributed program as a threaded one, because Rust and Go didn't have a distributed computing library, but says Go and Rust have "similar performance" in HPC.
He says he was surprised at the C performance, but there's no investigation of a cause. Maybe just because C is slow...
I don't mean to be overly critical, but these results in the paper mean absolutely nothing. It's a waste of time.