-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
draft learning objectives and possible references
- Loading branch information
Showing
5 changed files
with
98 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,23 @@ | ||
# Introduction | ||
|
||
We strive to create a sense of belonging by meeting participants where they are and embracing the idea that each of us is on a lifelong journey of learning. | ||
*Paragraph providing brief overview of this module* | ||
|
||
## Learning Objectives | ||
|
||
After completing this module, hackweek supporters will: | ||
|
||
* understand the importance of psychological safety to support creativity and open science | ||
* practice applying tools that support a healthy learning culture | ||
* identify specific ways we can maximize for inclusivity within existing hackweek structures | ||
|
||
## Possible References? | ||
|
||
Characteristics of open science collaborative culture {cite:p}`thibault_open_2023` | ||
|
||
Needed systemic changes to support a culture of open science {cite:p}`gentemann_opening_2022` | ||
|
||
Disclosure (vulnerability?) increases effectiveness of interracial mentoring relationships | ||
{cite:p}`leitner_reducing_2018` | ||
|
||
Trends in peer learning (do we need a separate helper section?) | ||
{cite:p}`topping_trends_2005` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,22 @@ | ||
# Introduction | ||
# Introduction | ||
|
||
*Paragraph providing brief overview of this module* | ||
|
||
## Learning Objectives | ||
|
||
After completing this module, project leads will: | ||
|
||
* understand the various roles that projects can play in supporting hackweek objectives | ||
* create a description for a project idea that is accessible for hackweek participants | ||
* practice facilitating small group team dynamics to ensure participants feel like they are contributing | ||
* be familiar with our suite of project [learning technologies](../technology/index.md) | ||
|
||
## Possible References? | ||
|
||
Evidence that project-based learning is a viable approach {cite:p}`almulla_effectiveness_2020`. | ||
|
||
Mentorship at a hackathon should be more than just occasional support. It should include taking ownership of the project, setting achievable goals, building social ties, and receiving learning-oriented support {cite:p}`nolte_how_2020`. | ||
|
||
Evidence that minimal guidance and lack of structure does not lead to positive project outcomes {cite:p}`irschner_why_2006`. | ||
|
||
## What to expect as a project lead |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,14 @@ | ||
# Introduction | ||
|
||
*Paragraph providing brief overview of this module* | ||
|
||
## Learning Objectives | ||
|
||
After completing this module, hackweek supporters will: | ||
|
||
* recognize the importance of project management and organizational support systems in achieving overall hackweek goals | ||
* have clarity on the milestones, deadlines and expectation of deliverables for their particular component of hackweek support | ||
* practice the norms of organizational behavior we aim to foster for hackweek participants | ||
* be familiar with the suite of technology platforms (Slack, GitHub) we use for managing hackweek activities | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,11 @@ | ||
# Introduction | ||
# Introduction | ||
|
||
*Paragraph providing brief overview of this module* | ||
|
||
## Learning Objectives | ||
|
||
After completing this module, hackweek supporters will: | ||
|
||
* have a comprehensive understand of the suite of technology tools used to support hackweek learners | ||
* understand how to use our technology tools within their specific supporting role (e.g. tutorial creation, project work) | ||
* know where to go for technology support before and during the hackweek |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,38 @@ | ||
# Introduction | ||
|
||
*Paragraph providing brief overview of this module* | ||
|
||
## Learning Objectives | ||
|
||
After completing this module, tutorial leads will: | ||
|
||
* create hackweek [learning objectives](https://www.sciencedirect.com/topics/social-sciences/learning-objective) using Bloom's Taxonomy | ||
* understand basic principles of adult learning | ||
* incorporate the appropriate level of interactivity into tutorial design | ||
* apply knowledge of pedagogical design to create tutorials at appropriate level of depth and complexity for the hackweek | ||
* gain experience in presenting tutorials in an engaging way | ||
* be familiar with our suite of hackweek [learning technologies](../technology/index.md) | ||
|
||
## Possible References? | ||
|
||
Tools for teaching with Jupyter {cite:p}`barba_teaching_2019` | ||
|
||
Active learning increases performance in STEM {cite:p}`freeman_active_2014` | ||
|
||
SWC lessons learned {cite:p}`wilson_software_2016` | ||
|
||
|
||
```{image} ../images/tutorials.png | ||
:alt: Tutorials in action | ||
:width: 500px | ||
:align: center | ||
``` | ||
``` | ||
|
||
## What to expect as a tutorial lead | ||
|
||
Hackweeks have traditionally been very dynamic events at which knowledge is exchanged in multiple directions across different levels of career position and backgrounds. We hope you will have an opportunity to learn a lot of new things by engaging in this experience. | ||
|
||
Past tutorial leads have used these events to gain teaching experience and as a way to round out their teaching profile. Like other participants you can also expect to build new contacts in the community, recruit students and generate new project ideas. | ||
|
||
In crafting a tutorial you'll gain valuable experience with creating reproducible computation examples. And together we'll collaborate on building digital content that will serve as a public resource with a citable DOI so that all tutorial authors receive credit for the effort! | ||
|