Feedback after teaching session 01/10/26 at UoM
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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!
- Linguagem predominante
- HTML
- Estrelas
- 25
- Forks
- 65
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de LibraryCarpentry/lc-python-intro
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
-
Ch10 Variable scope has confusing variable nameTalvez já em andamento @chennesy assumiu há 44 dias. Aberta
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 76/100
Todas as issues de LibraryCarpentry/lc-python-intro
Issues semelhantes
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
solidjs/solid-site#605 ·
Mantenedores costumam responder em até 1 dia
-
[ADD] GintaAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
aliammari1/awesome-ai-tools#592 ·
Mantenedores costumam responder em até 4 dias
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
-
guide
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
Mantenedores costumam responder em até 1 dia
-
New style: acid-graphicsAbertagood first issue new style
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
musicalbee/design-ontology#111 ·
Mantenedores costumam responder em até 1 dia