Feedback after teaching session 01/10/26 at UoM
還沒有人認領這個 Issue。
評估
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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!
- 主要語言
- HTML
- 星號
- 25
- 分支
- 65
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
LibraryCarpentry/lc-python-intro 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 88/100
-
Ch10 Variable scope has confusing variable name可能已有人在做 @chennesy 於 44 天前認領。 未關閉
難度 1/5 1 小時以內 新手友好度 88/100
-
難度 1/5 1 小時以內 新手友好度 88/100
-
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 1/5 1 小時以內 新手友好度 76/100
查看 LibraryCarpentry/lc-python-intro 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 88/100
solidjs/solid-site#605 ·
維護者通常 1 天內回覆
-
[ADD] Ginta未關閉
難度 2/5 1-3 小時 新手友好度 72/100
aliammari1/awesome-ai-tools#592 ·
維護者通常 4 天內回覆
-
難度 1/5 1 小時以內 新手友好度 88/100
-
guide
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
good first issue new style
難度 2/5 1-3 小時 新手友好度 82/100
musicalbee/design-ontology#111 ·
維護者通常 1 天內回覆