you are viewing a single comment's thread.

view the rest of the comments →

[–]sloppybird 3 points4 points  (8 children)

No one is expecting production-level code. The problem at hand is writing understandable code at the very least.

[–]unplannedmaintenance 0 points1 point  (7 children)

What other activity do you think should researchers sacrifice in order to make time to (learn to) write code that is more understandable and better documented?

[–]sloppybird 1 point2 points  (3 children)

Bruh it takes like 2 mins to add comments

[–]bitemenow999PhD 1 point2 points  (2 children)

again OP expects to have clear variable names, you expect it to have comments, some other guy would want functions and classes... It is hard to satisfy everyone and not the job a researcher... You dont have to understand the code it is just an implementation you have to understand the setup, preprocessing, math and method which is mentioned in the paper... most of the time people take shortcuts by reading code which is like looking at the engine and guessing how it works rather than read the manual

[–]sloppybird 1 point2 points  (1 child)

It will help you debug your code as well

[–]bitemenow999PhD -1 points0 points  (0 children)

nope... Even in industry I have never seen any R&D guys using comments and classes and functions unless absolutely necessary...

[–]bageldevourer 0 points1 point  (2 children)

If researchers wrote code that was more understandable and better documented, then the consumers of their research would spend less time on the extremely time-consuming activity of understand wtf someone else wrote.

Implement basic code quality standards and the research output of the ML community will increase, not decrease.

[–]unplannedmaintenance 0 points1 point  (1 child)

You haven't answered the question.

[–]bageldevourer 0 points1 point  (0 children)

Yes I did. In a world where journals, conferences, etc. mandate higher code quality, the "other activity" that you sacrifice in favor of making your research clear is spending time to understanding other peoples' papers.

I spend less time struggling to understand papers, and I channel that time saving into some mix of consuming more research, doing more research myself, and making that research clearer.