Instructor Training: Reference

Ключові моменти
Розвиток навичок за допомогою практики

  • Наша мета під час навчання новачків — допомогти їм побудувати корисні розумові моделі.

  • Це потребує практики та зворотного зв’язку.

  • Формуюче оцінювання забезпечує практику для слухачів і зворотний зв’язок для слухачів та інструкторів.
Експертиза та інструктаж
04 Coffee
Розвиток навичок за допомогою зворотного зв'язку
07 Lunch
Мотивація та демотивація
Мислення
10 Coffee
Welcome Back

  • Instructors guide learners to construct the proper big picture (accurate mental model) of the topic rather than focus on details.

  • Instructors rely on frequent feedback from learners to monitor their own presentation of the material.

  • Instructors introduce a few concepts at a time to avoid cognitive overload.

  • The best way to motivate learners? Show them how to do something they can immediately put to use and be enthusiastic about it.

  • Teaching is a learned skill.
Живе кодування – це навичка

  • «Кодування в реальному часі змушує інструктора викладати повільніше».

  • «Програмування дає учням постійну практику та зворотний зв’язок».

  • «Помилки, допущені під час спільного кодування в реальному часі, є цінними можливостями для навчання».
Preparing to Teach

  • To teach effectively, you have to know who you are teaching.

  • Good learning objectives communicate the intended effect of a lesson on its learners.

  • A good exercise provides useful guidance to instructors about next steps needed in teaching.
More Practice Live Coding

  • (Reflective) Practice makes perfect.
Managing a Diverse Classroom

  • Working with a broad range of learners can be challenging, but there are many ways to keep a classroom happy and motivated.

  • Response to a Code-of-Conduct violation at a workshop is subject to instructor discretion, but all violations should be reported to the Carpentries for follow-up.
Checkout Process

  • To certify, you must contribute to a lesson, take part in a discussion, and do a teaching demo within 90 days of your training event.
The Carpentries: How We Operate

  • Carpentry materials are all openly licensed, but Software and Data Carpentry names and logos are trademarked.

  • Carpentry workshops must cover core concepts, have at least one certified instructor, use our pre- and post-workshop surveys and report attendance information.

  • Guidance for teaching and hosting workshops is provided in The Carpentries Handbook.
Workshop Introductions

  • A planned introduction is a helpful tool in setting the workshop environment.

  • Introductions should both include practical information and start building relationships.
Putting It Together

  • Having a plan makes it easier for you to remember to implement the important teaching practices you’ve learned.
Wrapping Up

  • Feedback applies to all kinds of learning, including learning how to teach.

Books

Susan Ambrose et al: How Learning Works: Seven Research-Based Principles for Smart Teaching.
An excellent overview of what we know about education and why we believe it’s true, covering everything from cognitive psychology to social factors.
Stephen D. Brookfield and Stephen Preskill: The Discussion Book.
Describes fifty different ways to get groups talking productively.
Joshua Foer: Moonwalking with Einstein: The Art and Science of Remembering Everything.
Discusses memory techniques within the context of training for the U.S. Memory Championship. Compelling read and also very informative.
Elizabeth Green: Building a Better Teacher.
A well-written look at why educational reforms in the past 50 years have mostly missed the mark, and what we should be doing instead.
Mark Guzdial: Learner-Centered Design of Computing Education: Research on Computing for Everyone.
A well-researched investigation of what it means to design computing courses for everyone, not just people who are going to become professional programmers, from one of the leading researchers in CS education.
Doug Lemov: Teach Like a Champion 2.0.
Presents 62 classroom techniques drawn from intensive study of thousands of hours of video of good teachers in action.
Therese Huston: Teaching What You Don’t Know.
A pointed, funny, and very useful book that explores exactly what the title suggests.
James Lang: Small Teaching.
A short guide to evidence-based teaching practices that can be adopted without requiring large up-front investments of time and money.
Jane Margolis and Allan Fisher: Unlocking the Clubhouse: Women in Computing.
A groundbreaking report on the gender imbalance in computing, and the steps Carnegie-Mellon took to address the problem.
Claude M. Steele: Whistling Vivaldi: How Stereotypes Affect Us and What We Can Do.
Explains and explores stereotype threat and strategies for addressing it.

Papers

Baume: “Writing and Using Good Learning Outcomes”
A useful detailed guide to constructing useful learning outcomes.
Borrego and Henderson: “Increasing the Use of Evidence-Based Teaching in STEM Higher Education: A Comparison of Eight Change Strategies”
Describes eight approaches to effecting change in STEM education that form a useful framework for thinking about how Software Carpentry and Data Carpentry can change the world.
Brown and Altadmri: “Investigating Novice Programming Mistakes: Educator Beliefs vs Student Data”
Compares teachers’ opinions about common programming errors with data from over 100,000 students, and finds only weak consensus amongst teachers and between teachers and data.
Carroll, Smith-Kerker, Ford, and Mazur-Rimetz: “The Minimal Manual” Human–Computer Interaction, 3:2, 123-153, 1987.
Outlines an approach to documentation and instruction in which each lesson is one page long and describes how to accomplish one concrete task. Its focus on immediate application, error recognition and recovery, and reference use after training makes it an interesting model for Software and Data Carpentry.
Crouch and Mazur: “Peer Instruction: Ten Years of Experience and Results”
An early report on peer instruction and its effects in the classroom.
Deans for Impact: “The Science of Learning”
Summarizes cognitive science research related to how students learn, and connects it to practical implications for teaching and learning.
Guzdial: “Exploring Hypotheses about Media Computation”
A look back on 10 years of media computation research.
De Bruyckere et al: “Urban Myths About Learning and Education”
A one-page summary drawn from their book of the same name.
Gormally et al: “Feedback about Teaching in Higher Ed: Neglected Opportunities to Promote Change”
Summarizes best practices for providing instructional feedback and recommends specific strategies for sharing instructional expertise.
Guzdial: “Why Programming is Hard to Teach”
A chapter from Making Software that explores why programming seems so much harder to teach than some other standard subjects.
Kirschner et al: “Why Minimal Guidance During Instruction Does Not Work: An Analysis of the Failure of Constructivist, Discovery, Problem-Based, Experiential, and Inquiry-Based Teaching”
Argues that inquiry-based learning is less effective for novices than guided instruction.
Lee: “What can I do today to create a more inclusive community in CS?”.
A brief, practical guide on exactly that with references to the research literature.
Mayer and Moreno: “Nine Ways to Reduce Cognitive Load in Multimedia Learning”
Shows how research into how we absorb and process information can be applied to the design of instructional materials.
Porter et al: “Success in Introductory Programming: What Works?”
Summarizes the evidence that three techniques—peer instruction, media computation, and pair programming—can significantly improve outcomes in introductory programming courses.
Wiggins and McTighe: “UbD in a Nutshell”
A four-page summary of the authors’ take on reverse instructional design.
Wilson et al: “Good Enough Practices in Scientific Computing”.
Describes and justifies a minimal set of computing practices that every researcher could and should adopt.
Wilson et al: “Best Practices for Scientific Computing”
Describes and justifies the practices that mature scientific software developers ought to use.
Wilson: “Software Carpentry: Lessons Learned”
Summarizes what we’ve learned in 17 years of running classes for scientists.