Re:Challenge to scientists: does your ten-year-old code stil...
by SiempreViernes on Monday August 24, 2020 @12:42PM
(#24262410)
To clarify, nobody sees the code because they aren't allowed, or nobody ever ask to see it?
Re:Challenge to scientists: does your ten-year-old code stil...
by dandelion_lover on Monday August 24, 2020 @12:51PM
(#24262528)
The second case. However I am hesitating to ask to look at the code of my supervisor. How would I explain why I need it (if it's not needed for my research)? It's also unlikely user-friendly, so it would take a lot of time to understand anything.
Re:Challenge to scientists: does your ten-year-old code stil...
by bumby on Monday August 24, 2020 @01:07PM
(#24262746)
I think you touched on something important. Researchers are most concerned with “getting things working”.
One of my favorite points from the book Clean Code was that professional developers aren’t satisfied with “working code”, they aim to make it maintainable. Which may mean writing it in a way that is more clear and concise than we are used to
In other cases, a couple of other researchers may have a look at my code or continue its development. I worked with 4+ research teams and only saw one professional programmer in one of them helping the development. Never heard about a "dedicated software assurance team".