Hands'on Coding Session

🛠️ How we'll try to do things ...

Introductions

Each participants will be asked first to present him/her-self to the audience, with a very quick and formal presentation detailling coding background and current challenges (10 min max). Here is the proposed structure template :

1) Tools

• programming languages : which one do you know (master / medium / beginner), use in your current projects, how frequently, ...
• development environment : which one are you using (VSCode, PyCharm, Spyder, Vim, Gedit, Matlab, ...)
• computing systems : on what are you running simulations and experiments (laptop / work station / cluster, ...)

2) Targets

• problems of interests : which physics or applications, which kind of results are you looking for, ...
  
• types of code : are you a user or a developper, of solvers, optimization algorithms, ML models, ...
• usual runtimes : what is the typical wall-clock time for your simulation or experiments
  

3) Problematics and Issues

The significant one you already solved (past), the ones you are currently banging your head against the wall (present), and the ones that may scare you but are a problem for later (future).

4) Coding Culture

Concerning the following points

• git versionning
• testing
• code coverage
• continuous integration
• documentation
• AI-assisted programming (Github copilot, chatGPT, ...)
• performance benchmarking

How would you grade them :

1. never heard of it
2. from time to time
3. quite often
4. systematically

Of course, you don't have to necessary use slides for your presentation, and showing a simple text file summarizing all those points would be enough. Also, don't hesitate to quickly show some demos / examples that can describe to the audience your working context when coding ...