Mentoring Guide
Good mentoring is the heart of Python Weekend. Learn how to guide complete beginners with empathy, patience, and effective pedagogy—without taking over their keyboard.
⚠️ The #1 Rule of Python Weekend Mentoring
Never touch the attendee's keyboard or mouse. Even when you want to quickly fix a typo or indentation error, resist the urge. When you type for them, they lose confidence and ownership of their learning. Instead, verbalize where to look: "Check line 7—what do you notice at the end of the line?"
Our Core Mentoring Principles
Empathy & Beginners' Mindset
Remember when you first saw a terminal or got a SyntaxError. Concepts that feel obvious to senior developers (like file paths, strings, loops) are brand new foreign languages for beginners.
Ask Guiding Questions
Instead of giving answers directly, use the Socratic method: "What error message is the console printing?" or "What value do you expect this variable to hold right now?"
Celebrate Small Wins
Getting a variable to print, fixing an indentation error, or seeing their first function return a value are huge victories. Genuine encouragement builds resilience and joy.
Psychological Safety
There are no "stupid questions." Normalize mistakes: tell them developers spend 70% of their time fixing bugs, and errors are proof that they are learning.
Handling Common Workshop Situations
Scenario 1: One participant is much faster than the others in your pod
Give the faster participant optional challenge exercises or encourage them to explain concepts to their peer. Explaining code reinforces learning for both learners without leaving anyone behind.
Scenario 2: A participant is overwhelmed or experiencing impostor syndrome
Encourage a 5-minute stretch or tea break. Remind them that fatigue is normal, and validate their feelings: "Programming is intense when you first start. You've already written 20 lines of code today that you didn't know yesterday!"
Scenario 3: You encounter a bizarre bug you don't immediately know how to fix
This is the best teaching moment! Say: "I haven't seen this exact error before either—let's read the traceback together and figure out what it tells us." Demonstrating how a professional debugs is invaluable.
Mentor Do's and Don'ts
✅ DO
- Sit next to or slightly behind the attendee, at their eye level.
- Use plain language and explain acronyms (CLI, IDE, API).
- Praise curiosity and experimentation ("Try changing that number and see what happens!").
- Check in with quiet participants who might be hesitant to raise their hand.
❌ DON'T
- Never touch their keyboard or grab their mouse.
- Don't say "this is easy" or "obviously"—it diminishes their struggle.
- Don't introduce advanced computer science theory or framework debates prematurely.
- Don't show off complex one-liner shortcuts that confuse beginner readability.
Help Inspire the Next Cohort of Programmers
Interested in coaching at an upcoming workshop in your area? Let us know your availability and city!
Sign Up to Mentor »