Feedback after teaching session 01/10/26 at UoM
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 35/100
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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!
- Langage dominant
- HTML
- Étoiles
- 25
- Forks
- 65
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de LibraryCarpentry/lc-python-intro
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
-
Ch10 Variable scope has confusing variable namePeut-être pris @chennesy l’a pris il y a 44 jours. Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
-
Ch7 standardise loop variablesOuverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 76/100
Toutes les issues de LibraryCarpentry/lc-python-intro
Issues similaires
-
Ecosystem submission: Solid BitsOuverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
solidjs/solid-site#605 ·
Les mainteneurs répondent en général sous 1 jour
-
[ADD] GintaOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
aliammari1/awesome-ai-tools#592 ·
Les mainteneurs répondent en général sous 4 jours
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
-
guide
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
Les mainteneurs répondent en général sous 1 jour
-
New style: acid-graphicsOuvertegood first issue new style
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
musicalbee/design-ontology#111 ·
Les mainteneurs répondent en général sous 1 jour