workshop at Charité Universitätsmedizin Berlin

We have run the workshop in 6 morning sessions on 2, 3, 15, 16, 22 and 23 July 2025. We have split the session 3 into two sessions. We used VSCode as the IDE. 10 participants turned up.

In general feedback was very positive. Participants liked the scope, the structure and the online material. The pace was good. Participants particularly appreciate that the course materials are available as a website. Participants missed recommendations on using AI assisted programming. Perhaps I was a little negative about AI assisted programming.

I noticed that github has moved things around a little. Cards on the kanban board are now automatically issues associated with a project. Personally, I am not entirely convinced that debugging python is all that common. I had a chat with our python programmers who also only very rarely use the debugger. Python's REPL makes a debugger less necessary than for a compiled language. I ended up showing them how to use `pytest --trace` on the broken test.

In the last session I also talked about software publishing including using read-the-docs and zenodo for doi generation and mentioned JORS and JOSS.

I think next time I will look into using gitlab since we are using gitlab in house.

As instructor I very much enjoy running the course. We are planning to run this course once a year.

Das Issue hält Workshop-Feedback und zukünftige Ideen fest, nennt aber keine Datei, keinen Test und keinen Einstiegspunkt, der geändert werden soll. Beginne damit zu ermitteln, welche Kursmaterialien oder Projektdokumentation aktualisiert werden sollten; die Fertigstellung ist nicht definiert, weil der Bericht keine konkrete Verbesserung auswählt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.