1. Why feedback matters¶
Your feedback helps improve SDS320.
The Jupyter Book will evolve during and after the semester. Feedback helps identify explanations that are unclear, links that are broken, code that does not run, examples that need more context and topics where students need additional support.
Both positive and critical feedback are useful. Positive feedback helps identify what should be kept. Critical feedback helps improve the course for current and future students.
2. What kind of feedback is useful?¶
Useful feedback can include:
unclear or confusing explanations,
broken links,
figures or maps that do not display correctly,
code that does not run,
outdated instructions,
missing context,
typos or formatting issues,
sections that feel too fast or too detailed,
examples that could be more helpful,
suggestions for project support,
ideas for future lessons or resources.
Brief feedback is fine. A short note such as “The explanation of raster masks was unclear to me” can already be helpful.
3. How to give feedback¶
You can use different channels depending on the type of feedback.
General course feedback¶
For general impressions, reflections and ideas, use the SDS320 Padlet feedback board:
For improved visibility of the Padlet, follow this link.
You can structure your feedback using:
I like — What worked well? What helped your learning?
I wish — What was missing, unclear or difficult?
I wonder — What ideas, questions or suggestions do you have?
Specific page or content feedback¶
If your feedback relates to a specific page, section, code cell, figure or link, please report it as directly as possible.
You can use the relevant MS Teams channel to flag the issue.
If the course website has an “Edit this page” ✏️ icon at the top, you may also suggest small corrections directly through GitHub.
4. Thank you¶
Thank you for helping improve the course.
SDS320 is a new and evolving course. Your feedback directly shapes how the Jupyter Book, examples, project guidance and learning activities develop over time.