Feedback after teaching session 01/10/26 at UoM
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
This issue reports teaching feedback but does not identify a specific change or file. Start by reviewing the lesson episodes and the suggested priorities, including plotting, environments, scripts, and JSON examples. Agree on a concrete scope with the maintainers before making changes; done should mean that an agreed lesson update addresses that scope.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Hiya! We taught this course yesterday at University of Manchester after a request from our university library. Firstly, thanks so much to everyone who has contributed so far!
The trainers were from our Research Software Engineering team, a central team supporting researchers across all domains (i.e. not library staff). There were 15 learners, maybe 5 of whom were from the library and the rest were either postgrad students or research staff, normally from humanities or biological sciences (i,e. people who didn't study coding at undergrad).
Generally it went well, we normally teach the software carpentry version but this seemed like a bit of a gentler introduction for our target audience, and we really like introducing people to pandas.
We had 5 hours of teaching time scheduled. About the first half hour of this gets eaten up by an introduction and making sure everything can use the jupyter notebooks (we have an online system). So 4 1/2 hours. We got through episodes 2 - 8 doing all the exercises, then 9&10 with just one exercise each. We skimmed through Ep12 because we ran out of time, and we figured it's quite straightforward for self-learning after the course.
We looked through the notes beforehand and decided we wouldn't have time for Ch11, but also that this was the lower priority chapter. I was a bit surprised this is in an introductory course. Ep12 was definitely a higher priority for us, and I wonder if things like more detail/examples on plotting, manging environments, running a .py file as a script, example of different file types like JSON would be more useful for our typical learners? But we are not library scientists, I am generally wanting to teach "Introduction to data analysis in python" or something like that, rather than necessarily anything specifically to do with libraries
We have collated some feedback from the trainers and hopefully will get some from the learners, and I'll make some issues about specific things, possibly even some PRs
Thanks again and I hope this feedback is useful!
- Vorherrschende Sprache
- HTML
- Sterne
- 25
- Forks
- 65
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus LibraryCarpentry/lc-python-intro
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
-
Ch10 Variable scope has confusing variable nameEvtl. vergeben @chennesy hat das vor 44 Tagen übernommen. Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 76/100
Alle Issues in LibraryCarpentry/lc-python-intro
Ähnliche Issues
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
solidjs/solid-site#605 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[ADD] GintaOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
aliammari1/awesome-ai-tools#592 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
-
guide
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
New style: acid-graphicsOffengood first issue new style
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
musicalbee/design-ontology#111 ·
Maintainer antworten meist innerhalb von 1 Tag