Peer
Training

Jeff Anderson's learning zone model: between boredom (comfort zone) and shutdown (survival zone) is the Sweet Spot — where productive struggle happens. 'Full Ignition' = when a student hits the sweet spot and can't stop learning. Your job as a tutor is to calibrate: keep them challenged but not overwhelmed.

Complete foundational work before passion projects. In tutoring: make sure the student has done the core reading/assignment before jumping to the fun stuff. The student who skips veggies builds on sand. Connect to 'career capital' (Cal Newport): you earn the right to do creative work by first mastering the fundamentals.

Freire's banking model: the instructor deposits knowledge into the student's empty head. Dialog: knowledge is co-constructed through conversation. In tutoring, you are not a knowledge dispenser. You are a thinking partner. Ask questions. Don't give answers. The student must do the cognitive work.

Tall & Vinner's framework: a student's 'concept image' (their mental model) often differs from the formal definition. 'Abuelita language' = explaining in plain, personal terms. A student might say 'a stack is like a pile of plates' — that's a concept image. It's useful AND incomplete. Your job: honor the image, then extend it.

The testing effect: retrieving information from memory strengthens it more than re-reading. In tutoring: don't re-explain. Instead, ask the student to recall. 'What do you remember about binary search?' is more powerful than 'Let me explain binary search again.' The struggle to recall IS the learning.

'White time' vs. 'Mexican time.' 'Professional' communication vs. how you talk at home. Code-switching is survival — and it's exhausting. As a tutor, be aware that the student may be performing a version of themselves that isn't natural. Create space for their actual communication style. Don't enforce 'professional' as the only valid register.

Jeff Anderson's framework: first navigate the system (earn the grade, get the degree, protect yourself), then transform it (change policies, build alternatives). Ungrading is anti-oppressive because traditional grading is labor exploitation — students produce work, instructors assign value, students have no power to negotiate. Tutors help students navigate AND name the system.

Build durable artifacts, not disposable assignments. A 'Capture System' (Tiago Forte) collects insights, code snippets, project ideas, and connections over time. Writing your own textbook — compiling your notes into a reference you'd actually use — is the ultimate portfolio piece. The goal: in 10 years, your portfolio demonstrates not what grades you got but what you built and learned.

Scenario: A student comes in visibly stressed. They're behind in three classes, considering dropping CS, and say 'I'm just not smart enough for this.' They don't need a CS explanation right now. They need to be heard, to have their experience validated, and to be helped to make a strategic decision — not an emotional one.

Scenario: A student submits code that is clearly AI-generated. They're not cheating for fun — they're in survival mode. The assignment is due in 2 hours, they work 30 hours/week, and they don't understand the material. Punishment won't help. The question is: what structural support was missing that made this the rational choice?

Scenario: A student emails asking for an add code to your section. The class is full. Institutional policy says no. But this student needs this class to transfer on time. What are your options? What power do you have? What power don't you have? This is system navigation in real time.

Math: a 1-hour tutoring session with 8 students = 7.5 minutes per student. Subtract transition time = 6.25 minutes of actual attention per student. At a 40:1 student-to-tutor ratio, you have even less. This is the structural reality. It means every minute must count. Triage. Prioritize. Don't try to re-teach the entire lecture.

Scaffolding = temporary support that you remove as the student grows. Spoon-feeding = doing the cognitive work for the student. The difference: scaffolding ends with the student doing the thinking. Spoon-feeding ends with the student having the answer but not the understanding. The test: could the student solve a similar problem without you?

The Socratic method in CS tutoring: instead of explaining, ask questions that lead the student to discover the answer. 'What would happen if the list were empty?' 'What does this line return?' 'Can you trace through this with a specific example?' The goal: the student has the 'aha' moment, not you.

Most students see error messages as failures. Reframe: error messages are the most precise feedback a computer can give. 'IndexError: list index out of range' tells you exactly what happened and where. Your job: teach the student to read the error before asking for help. The error IS the teacher.

AI analogy: asking ChatGPT to write your code is like asking a robot to do your push-ups. The robot gets stronger. You don't. The value of CS assignments is not the code — it's the thinking process that produces the code. If you skip the process, you skip the learning. Use this analogy when students ask 'why can't I just use AI?'

Anderson's parable: Sven is a master carpenter. He doesn't use a nail gun for every joint — he knows which joints need screws, which need glue, which need nails. His mastery comes from understanding the material, not from the tool. Similarly, a CS student who understands data structures deeply can choose the right one for any problem. The tool (Python, Java) is secondary to understanding.

Donald Knuth offers $2.56 for every error found in The Art of Computer Programming. The message: finding errors is valuable, not shameful. Build this culture in your tutoring: celebrate when a student finds a bug. Make error-finding a sport, not a punishment. The student who finds errors is paying deeper attention than the student who doesn't.

Scenario: A student comes to every session but barely speaks. They nod, they write, but they don't ask questions or engage. Are they learning? Are they lost? Are they culturally conditioned to be quiet in academic settings? Don't assume silence means understanding OR confusion. Create low-stakes entry points: pair share, written responses, thumbs up/down.

Try this: attempt to learn something genuinely new and hard for 30 minutes. Not CS — something where you're a total beginner (a new language, a musical instrument, advanced math you never took). Notice: the confusion, the frustration, the impulse to quit, the feeling of being 'stupid.' That is what your students feel. Every session. Remember it.