Teachers from Tufts, Duke and Loyola Marymount show their GitHub workflows at SIGCSE 2018
Nearly every conversation the GitHub Education team had with teachers at SIGCSE 2018 (Special Interest Group on Computer Science Education) touched on the themes of communication, iteration, and real-world tools.…
Nearly every conversation the GitHub Education team had with teachers at SIGCSE 2018 (Special Interest Group on Computer Science Education) touched on the themes of communication, iteration, and real-world tools. This year at SIGCSE we had two special sessions on those themes: three teachers walked through their GitHub workflows, and four students shared their experiences outside the classroom.
Teacher panel: Real-world tools, engaged students
Git has a learning curve for students (and teachers)! In this series of talks, teachers shared why they choose to use Git and GitHub and how it benefits their classroom.
Or skip to a specific section:
- 2m50s: Ming Chow, Tufts University
- 18m30s: Dr. Mine Çetinkaya-Rundel, Duke University
- 36m00s: Dr. John David Dionisio, Loyola Marymount University
Student panel: Outside the classroom
Hear students speak about using GitHub and the benefits of GitHub Education on their campuses.
Or skip to a specific section:
- 2m15s: Amy Dickens, University of Nottingham
- 18m20s: John Pham, University of California, Riverside
- 27m45s: Chris Cannon, North Carolina Agricultural and Technical
- 42m00s: Elliot Whitehead, University of Colorado, Boulder
Sign up for lesson plans, tutorials, and best practices from GitHub Education
Once a month we’ll pass along tips and tricks for implementing Git and GitHub in your classroom.
Written by
Related posts

GitHub Copilot: Meet the new coding agent
Implementing features has never been easier: Just assign a task or issue to Copilot. It runs in the background with GitHub Actions and submits its work as a pull request.

Code. Create. Commit. Welcome to dev/core
The new GitHub Shop collection is here. We’re celebrating you.

GitHub Availability Report: April 2025
In April, we experienced three incidents that resulted in degraded performance across GitHub services.