katrinleinweber
commented
5 years ago In case someone brings up the need to write a small program, we should approach this task in a way that helps other attendees generalise to their own requirements. For example:
- nailing down what functionality of the program is actually required vs. what is "nice to have"
- preparing pseudo-code as comments in the source-code file
- version-controlling it right away
- programming in a portable way, e.g. project-based
This will likely mean that 2h are not sufficient, but we should try to lay a solid & FAIR groundwork there, rather than try and rush towards a possible solution. We can always schedule follow-up sessions individually.
These sessions / events are open to any kind of topic, question, problem, idea, etc. around research data or software.
Attendance on Oct.24th: 7