Notices by Hugo Lefeuvre (hle@mstdn.io)

@clacke This tends to make researchers cut corners whereever they can. Scientific conferences do not really value code quality (it’s “engineering” not research), so researchers tend to cut corners on code quality.

IMO fixing that requires more profound changes in the functioning of academic research

@clacke The main one is probably the pressure to output. As academics, especially junior ones, we need to publish, often, and at top tier venues (which are extremely competitive). If you’re working on a hot topic, it’s even more competitive - you want to be the first to have your fresh new idea published out there.

@clacke @clacke Manchester here :)

Interesting discussion! Personally I have always tried to make my research code as open and reusable as possible. And I think that it sort of worked? We even got an award for that.

It’s super hard though. And I’d argue that it’s not because of a lack of skills (at least in my field, systems software and security).