# 001 Internal

- Intro
- Show an old code that can be improved: https://github.com/rkdarst/pcd/
- Show a newer code that's a little bit better: https://github.com/dftlibs/numgrid/
- Q&A
- Demo: Archiving and citing software using Zenodo: https://github.com/bast/smeshing → https://zenodo.org/record/3774421
- git-pr: pull requests with fewer keystrokes: https://github.com/NordicHPC/git-pr
- tldr: simplified, example-driven manual pages: https://tldr.sh/
- Q&A and conclusions
- Epilogue discussion

- (00:00) intro
- welcome and who we are
- coderefinery project and workshops
- why we start this: fun, learning, mix of everything
- this is first time so perhaps we experience rough edges
- we are not super experts in everything but that's not the point
- (00:05) show something from our past to be improved
- Richard shows an old code and we discuss
- (00:15) either show a good example or teach something
- Radovan
- numgrid
- Encourage participants to submit their code for review
- (00:25) questions and answers
- teach hackmd
- answer questions
- What do you know now, that you wish someone had taught you?
- Radovan: Enrico's quote that i will be collaborating with myself, citation, documentation, sharing
- (00:35) teach something
- software citation, putting code on zenodo
- (00:45) we show each other something
- Richard "spontaneously" demonstrates git-pr
- Radovan shows tldr
- (00:50) together:
- Questions if there are any
- What do you know now, that you wish someone had taught you?
- Radovan: stateless functions, type safety
- Stump us! One hard question which we'll answer for next week.
- wrap-up
- ask for code submissions for next time

## Other ideas
- "commercial breaks" where we fill people in again
- questions
- guidance on what makes a good question
- rsh-notes issues and labels about things
- Point out good youtube talks to listen to
- "random topic" decided by listener, we teach without preparing any
- interviews
- *EG* (reseachers), management, RSEs in groups, developers,
- do you think that software production is rewarded well, relative to the value it has?
- Every time we teach the value of open science, we end with "but you probably don't have the right to open your own work without asking for permission... and good luck with that!" What can we do about this?
- how has software changed during your time?
- a few funny questions, pick which ones you want to answer
- what do you know now, that you wish someone had taught you when you started?
- polls to decide next topic
- talker/moderator
- stream schedule, google calendar
- record and post
- pair programming
- emphasize it's about
- timestamp videos when posted

Tasks:
- find "old" code to show
- find some good code
- go through the rsh notes and add labels
- 1 backup topic
- table of "standard topics"
- write hackmd instructions, ready to paste in
- make some commercial breaks