Feedback after teaching session 01/10/26 at UoM
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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!
- Lingua principale
- HTML
- Stelle
- 25
- Fork
- 65
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di LibraryCarpentry/lc-python-intro
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
Ch10 Variable scope has confusing variable nameForse già presa @chennesy l’ha presa 44 giorni fa. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 76/100
Tutte le issue di LibraryCarpentry/lc-python-intro
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
solidjs/solid-site#605 ·
I maintainer di solito rispondono entro 1 giorno
-
[ADD] GintaAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
aliammari1/awesome-ai-tools#592 ·
I maintainer di solito rispondono entro 4 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
guide
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
New style: acid-graphicsApertagood first issue new style
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
musicalbee/design-ontology#111 ·
I maintainer di solito rispondono entro 1 giorno