Step 331. Starting to Mentor — Learning by Teaching: If You Can’t Explain It, You Don’t Know It

Level 4 — Professional | Difficulty ★★☆☆☆ | Estimated time: 2 days (recruiting a mentee + preparing and running the first session) + weekly ongoing sessions thereafter

Prerequisites: Step 329’s new-technique notes, Step 330’s summary notes — teaching material must be stacked in your warehouse. Step 297’s retrospective experience also helps.

What you need: a mentee candidate (a junior from a club, a beginner from an online community), a video-call or offline meeting tool, and notes for session records. This chapter is a people exercise, so every screen is a screen example.
Caution: mentoring is not a one-way lecture but a conversation. Never disclose a mentee’s personal information or progress without consent.
⚠️ All exercises in this chapter are for your own lab and legal platforms only. Applying them to unauthorized systems is a crime. Pass this same principle on verbatim when guiding a mentee through lab environments.

Teach someone and the holes in your knowledge reveal themselves with precision. If you stall somewhere when asked "please explain buffer overflows," that stall is exactly what you don’t know. This is the Feynman technique — Nobel laureate Richard Feynman’s learning method, whose gist is "if you can’t explain it to someone else, you haven’t understood it."

And mentoring is not an activity where only you learn. A junior’s "questions about the obvious" make you re-examine foundations you’d forgotten, and donating knowledge becomes reputation and network in the community. Today you open the first session of a weekly mentoring routine — how to find a mentee, designing the first session, and the recording method that turns sessions into your own learning engine. The whole cycle.

1. Learning Objectives

By the end of this chapter, you will be able to:

Explain the Feynman technique’s principle and argue why mentoring is "the best review"
Execute the three routes for finding a mentee, plus the fallback (a study-group talk) when none works
Design the first session’s composition (level assessment → goal agreement → first topic)
Record "points where I stalled while explaining" after a session and convert them into my reinforcement list
Explain the nature of impostor syndrome ("am I good enough to teach?") and how to handle it

2. Background Knowledge — Today’s Tools and Concepts

Today’s Tools at a Glance

Category	Details
Language/environment	Video call or an offline space, screen sharing (for watching over lab work), session-record notes
Today’s command	Forms, not commands — the level-assessment questionnaire, the session-structure table, the stall-point record
Concepts needed	Feynman technique, level assessment, impostor syndrome, accumulation of session materials
Today’s deliverable	First mentoring session completed + recurring schedule confirmed + a session-record document

2-1. The Feynman Technique — Explaining Is the Test

Understanding is only a claim until tested. Solo study’s test (solving problems) tells you where you’re wrong, but explaining tells you where you stall — and the stall point is the exact coordinate of what you don’t know.

The Feynman technique’s procedure has four steps. ① Pick a concept and explain it as if to a beginner. ② Mark the points where you stall or flee into jargon. ③ Re-study only those points. ④ Explain again from the start — this time in analogies and plain words. Mentoring performs steps ①–② of this procedure in front of a real person. The imaginary beginner is forgiving; a real mentee’s "but why is that?" is precise.

2-2. Mentoring’s Triple Return — Review, Foundation Recheck, Reputation

The reasons mentoring is "the best review" come in three layers.

Return	Mechanism
Discovering knowledge holes	The point where you stall while explaining = the coordinate of what you don’t know
Foundation recheck	The mentee’s "questions about the obvious" make you re-examine forgotten basics
Reputation and network	Donated knowledge accumulates as trust in the community

The second return is surprising. A mentee asks from the level of "what’s a login?" — and answering requires unrolling assumptions you passed so long ago you’ve forgotten them ("surely they know what a cookie is"). Without this recheck, cracks in the foundation grow quietly beneath advanced techniques.

The third return is bought with time. Once a weekly session has stacked for a few months, your name stays in the community as "someone who answers questions." That trust later becomes the first name that comes to mind for team building, competition-team recruiting, and even career opportunities.

2-3. Who Is the Mentee Looking For — "Someone Just a Little Further Down the Path"

What a mentee wants is not a flawless expert. A mentee needs someone who walked the path just a little earlier — someone who crossed last week the very stretch you were wandering until yesterday.

This fact is the antidote to impostor syndrome ("am I good enough to teach?"). If you can explain it to yourself back at Step 1, you’re already qualified to teach. You have completed this book’s Step 1 through 330 — someone holding that map can be a better guide to a person wandering Step 30 mapless than the world’s best expert. The world’s best has forgotten that path; you remember it.

2-4. Accumulating Session Materials — Today’s Mentoring Is Tomorrow’s Lecture

Don’t discard each session’s slides and lab guides — accumulate them. These materials later become lecture and talk material — the raw-material warehouse for the very next chapter (Step 332, seminar talk materials).

The accumulation rule is one: on the day a session ends, reflect the mentee’s questions into the materials. "This question came up" means "this material’s explanation was insufficient" — so questions are a free review of your materials.

Accumulation has one more side effect — making progress visible. When session materials stack neatly in one folder, "what I have taught" shows at a glance. That list later becomes the "teaching experience" entry in your portfolio and the track-record evidence in a talk proposal. Records of teaching are evidence of the giving act — and simultaneously your asset list.

3. Follow Along

3-1. Finding a Mentee — Three Routes and a Fallback

Find a mentee through three routes.

Mentee recruitment routes (screen example):
Route 1. Juniors in a school/work security club — announce "I've completed
        330 days of this book; I can watch over a beginner's first 4 weeks"
Route 2. The beginner channel of an online security community (a security
        Discord server, etc.) — post "mentee wanted" on the "mentor wanted" board
Route 3. This book's reader meetup/study group — someone who just started
        reading the same book
Fallback: if no mentee is found, start with a "study-group talk" —
        the audience is the pool of potential mentees

How to read it: the core of the recruitment message is the frame of "someone who went ahead," not "expert." "Let me teach you" loses to "let me help you shorten the path I wandered" — more honest, and a higher response rate.

3-2. Preparing the First Session — The Level-Assessment Questionnaire

Half of the first session is level assessment. Teaching blind wastes time. Here’s a questionnaire example.

Mentee level-assessment questionnaire (screen example):
1. Programming experience: (none / took an intro course / can write simple scripts)
2. Linux use: (first time / a few commands / daily use)
3. Progress in this book: (not started / up to Step ~N / progressing with skips)
4. Security knowledge: terms they know — (can they explain the difference
   between hashing and encryption)
5. Goal: (curiosity / school or employment / CTF / bug bounty)
6. Hours available per week: ( ) hours

How to read it: #6 matters most. However grand the goal, a mentee with 2 hours a week needs a curriculum fitted to it — and without knowing this number, the mentoring evaporates within two months. And #4 — a check question like "the difference between hashing and encryption" filters out self-assessment illusions.

With the questionnaire answered, build the first 4 weeks’ plan together based on the answers. A mentee whose goal is "employment" and one whose goal is "curiosity" must read the same book in a different order, and 3 hours versus 10 hours a week means different assignment volumes. This agreement is the first session’s deliverable — a plan the mentor set unilaterally gives the mentee no reason to keep it, but a plan set together becomes a promise.

3-3. Session Structure — Designing a Weekly 90 Minutes

The standard structure of a recurring session.

Weekly session structure (screen example):
[00–10 min] Review of last week — the mentee explains the last topic
            "to me" (role reversal!)
[10–40 min] Today's topic — one topic only, including a demo in my lab
            via screen share
[40–70 min] Mentee follow-along — the mentee shares their screen and
            operates; I watch and give hints
[70–85 min] Q&A — free questions; unknowns get recorded as "answer after
            checking"
[85–90 min] Next week's preview and assignment

How to read it: the role reversal in the first 10 minutes is this structure’s heart — having the mentee explain applies the Feynman technique to them too, and you measure the mentee’s understanding state precisely. "Having the mentee explain to me" is the best assessment tool a mentor has.

3-4. Recording Stall Points — My Reinforcement-List Generator

Record on the day the session ends. Here’s a form example.

Session record (screen example):
[Session #3 — date]
- Topic: the concept of buffer overflow + first lab
- Mentee response: followed up to the stack diagram; stalled at "why does
  overwriting EIP stop the program"
- Point where I stalled while explaining: I, too, grew clumsy trying to
  re-explain "why overwriting the return address is control hijacking"
  starting from how CALL/RET works
- → My reinforcement list: organize assembly CALL/RET and stack frames
  into a single diagram
- Mentee's good question: "how would an attacker know the buffer size in
  the first place?" — made me rethink the paths information leaks
  regardless of canaries

How to read it: the "point where I stalled while explaining" field is this record’s purpose — that’s my reinforcement list, the item to process in Step 330’s weekly routine. The "mentee’s good question" field is evidence that 2-2’s second return (foundation recheck) actually fired.

3-5. Accumulating and Improving Session Materials

Stack each session’s materials (slides, lab guide) in a folder, and improve them the same day per 2-4’s rule.

Material accumulation folder (screen example):
mentoring/
  session01_linux_basics/    slides.md, lab_guide.md, feedback.md
  session02_web_http/        slides.md, lab_guide.md, feedback.md
  session03_bof_concept/     slides.md, lab_guide.md, feedback.md
  ...
  README.md                  <- session list and mentee progress summary

How to read it: why feedback.md exists per session — because 3-4’s records (stall points, good questions) are the input for the next improvement. Once about ten of these 3-file sets stack up, that is the manuscript warehouse for Step 332’s seminar materials. Mentoring is not an activity that ends in itself — it’s also the test run of your talk materials.

4. Missions & Exercises

Mission — Open Your First Mentoring Session

Recruit 1 mentee via one of 3-1’s routes (if none, substitute the study-group-talk format and record that fact).
Assess and document the mentee’s level and goals with 3-2’s questionnaire.
Run the first session in 3-3’s structure — pick the topic from the mentee’s questionnaire results.
Fill out 3-4’s record form on the day of the session — the "point where I stalled while explaining" field must not be left blank.
Agree on a recurring schedule (weekly, day and time), register it in your calendar, and create the session-materials folder (3-5).

Exercises

Exercise 1. Explain why the Feynman technique’s test (explaining) gives different information than solo testing (solving problems), through the difference between "where you’re wrong" and "where you stall."

Exercise 2. Explain why "someone who walked the path just a little earlier" can be a better guide for a beginner than the world’s best expert.

Exercise 3. Give two reasons why 3-3’s session structure has the mentee explain the previous topic to the mentor in the first 10 minutes.

Exercise 4. Explain which of mentoring’s returns disappears if you don’t record "points where I stalled while explaining," and how that record connects to Step 330’s routine.

5. Model Answers & Completion Criteria

Mission Model Answer

Check against these verification criteria.

Honesty of recruitment: does the mentee actually exist — if substituted with a study-group talk, are the circumstances recorded.
Completeness of the questionnaire: are all 6 items (especially hours per week) answered.
Session structure: were the 5 blocks (review, explanation, follow-along, Q&A, assignment) kept with their timings — especially the first 10 minutes where "the mentee explains."
Same-day recording: is the record written on the session day — memories days later erase the "stall points."
Devices of regularity: do the calendar registration and materials folder exist.

Exercise Answers

Answer 1. Problem solving is a test with a fixed answer — it tells you "you were wrong," but which link broke must be backtraced by yourself, and if you skip the problem you got wrong (moving on without realizing you don’t know), the test never fires at all. Explaining is a test with no answer key — you must reconstruct the causal chain of knowledge from the start, and your speech stops where the chain is broken; that stop is the coordinate of the broken link. Because explaining is the only test that exposes the difference between "roughly knowing" and "being able to explain," the Feynman technique places explanation as learning’s final gate.

Answer 2. The expert passed the beginner’s path too long ago and has forgotten where it’s hard — the expert’s list of "obvious things" is so long that what needs explaining is itself invisible (this is called the curse of knowledge). Someone who walked the path just a little earlier crossed it last week, so they remember which stone they tripped on. The accuracy of an explanation often depends not on depth of knowledge but on memory of the traps — and that memory is erased with time. Your greatest asset right now is 330 days’ worth of fresh trap memories.

Answer 3. First, the Feynman technique applies to the mentee too — being made to explain moves their understanding from "something heard" to "something sayable." Second, it’s a precise assessment tool for the mentor — the point where the mentee’s explanation stalls sets today’s reinforcement target. A questionnaire is self-report, so illusions mix in; explaining is live performance, so there’s no illusion. Mentoring without these 10 minutes becomes the mentor’s one-way recitation, leading to the accident of marching through progress without knowing the mentee’s actual state.

Answer 4. Mentoring’s first return — "discovering knowledge holes" — disappears. Stall points fade from memory quickly once the session ends, so without same-day recording only the feeling "something was hard" remains while the coordinates vanish. A recorded stall point becomes a reinforcement assignment to process in Step 330’s weekly reading routine — this week, find and read material on that topic, write a summary note, and re-explain it in the next session. When this loop (stall → record → routine reinforcement → re-explanation) turns, mentoring is both a donation of knowledge and simultaneously a self-learning engine.

Completion Criteria Checklist

[ ] I recruited 1 mentee (or recorded the study-group-talk substitution)
[ ] I documented the mentee’s level, goals, and weekly available hours with the level-assessment questionnaire
[ ] I ran the first session in the 5-block structure (review, explanation, follow-along, Q&A, assignment)
[ ] I gave the mentee time to explain to me in the session’s first 10 minutes
[ ] I wrote the record on the session day and filled in "points where I stalled while explaining"
[ ] I registered the stall points as reinforcement assignments in Step 330’s weekly routine
[ ] I agreed on a weekly recurring schedule and registered it in my calendar
[ ] I created the session-materials folder (slides, lab_guide, feedback) and started accumulating

6. Common Pitfalls & Fixes

Wall 1. The thought "am I good enough to teach?" keeps me from recruiting

Symptom: you write and delete the mentee-wanted post over and over.

Cause: impostor syndrome — as skill grows, the "list of things I don’t know" grows with it, so more skill paradoxically lowers self-assessment.

Fix: re-read 2-3 — a mentee is looking not for a flawless expert but for someone who walked the path just a little earlier. And change the criterion: not "is there nothing I don’t know?" but "can I explain it to myself of this journey ago?" You have completed this book’s 330 assignments — if you can’t convey that process to someone just starting, who could? For questions you don’t know, "I don’t know; I’ll check and get back to you" is the correct answer — that sentence doesn’t erode a mentor’s trust; it builds it.

Wall 2. My mentee stopped showing up — it fizzled out in a few weeks

Symptom: after 2–3 sessions the mentee’s replies grow sparse and the sessions die.

Cause: mostly a curriculum mismatched with the mentee’s reality (weekly hours, level) — often the case where the questionnaire’s #6 (weekly hours) was ignored and progress marched at the mentor’s pace.

Fix: check three things. ① Assignment volume — are you assigning at or below half the mentee’s weekly available hours? A mentee who can’t complete assignments avoids sessions out of guilt. ② Cycle of achievement — does every session have one "thing that worked today"? Four weeks of pure theory and they vanish. ③ Renegotiating the contract — directly ask "is the current pace working?" around session 3–4 and adjust. Mentoring’s death is mostly a design problem, not the mentee’s willpower problem.

Wall 3. A question I couldn’t answer came up mid-explanation and I froze

Symptom: a one-notch-deeper question like "so what about in TLS?" stops your answer.

Cause: normal — this is itself the reason for mentoring (2-1). The problem is not stalling but how you handle the stall.

Fix: memorize the three-step procedure. ① Admit it on the spot — "good question; I don’t know it precisely myself." ② Record it — immediately write it in the session record’s "stall point" field. ③ Promise a follow-up and keep it — say "I’ll check and get back to you before the next session," and without fail follow through. The only forbidden response is bluffing through — it plants wrong knowledge in the mentee, erodes your trust, and above all erases a precious reinforcement coordinate with your own hands.

Wall 4. Session prep eats too much time — a full day for a 90-minute session

Symptom: building session materials from scratch every week makes mentoring a burden.

Cause: the ambition to make materials "finished products" — a first version of materials may be rough.

Fix: use the material warehouse — Step 329’s new-technique notes, Step 330’s summary notes, and the labs you followed along in this book are directly the manuscript for session materials. Session materials are your chapter notes thinly edited to the mentee’s level. And trust 2-4’s rule — incremental improvement by reflecting post-session questions into materials. A rough material improved ten times beats a finished product made once.

Wall 5. My mentee mentions a real service as a lab target — how far should I help?

Symptom: a question like "can I test my school’s website?" comes up.

Cause: it’s normal for a mentee to not yet have a sense of the legal boundary — and conveying that sense is also a mentor’s job.

Fix: draw the line firmly and clearly, and present alternatives. Unauthorized systems — including the school — are absolutely off-limits; convey this chapter’s opening notice verbatim. Instead, guide them to legal paths — this book’s lab environments, legal platforms (CTFs, wargames), and later the bug bounty scope concept (Step 314). Teaching a mentee "what must not be done" is as much mentoring content as "what can be done."

7. Summary

Today’s Concepts

Concept	One-line explanation
Feynman technique	If you can’t explain it, you don’t know it — explanation is knowledge’s final test
Curse of knowledge	Experts forgetting beginners’ traps — the value of "someone just a little further down the path"
Level-assessment questionnaire	Especially weekly hours — the core variable of mentoring survival
Role-reversal review	The mentee explains to the mentor — the best assessment tool
Stall-point record	The mentor’s reinforcement-list generator — same-day recording is life
Impostor syndrome	Self-doubt growing alongside skill — countered by resetting the criterion

Today’s Tools & Commands

Tool/form	What it does
3 mentee-recruitment routes	Club juniors · online communities · reader study groups
Level-assessment questionnaire	Prior measurement of level, goals, weekly hours
90-minute session structure	Review (role reversal) · explanation · follow-along · Q&A · assignment
Session-record form	Same-day record of stall points + good questions
Materials folder	Accumulating the 3-file set: slides, lab_guide, feedback
Unknown-question 3 steps	Admit → record → follow through

The Core Instinct

A few weeks into mentoring, a strange experience comes — you went to teach and feel you learned more. The map of your knowledge the stall points revealed, the foundations the mentee’s questions unrolled again, and the soft deadline pressure of having to find answers before the next session. Mentoring is the most efficient learning device wearing the shape of a giving activity.

Remember one more thing — a first mentoring session is awkward by definition. A first session with rough explanations, broken time allocation, and fumbled answers is not a failure but a baseline. The session-record form preserves that baseline, so at your tenth session, open the first record again. That difference is the growth curve of teaching skill — a new kind of skill grown on top of the skill this book’s 330 assignments built.

And remember the accumulated session materials — they become the manuscript for the next Step 332’s seminar talk materials and Step 333’s public talk. The path by which explaining in front of one person grows into a talk in front of thirty is laid on top of this weekly session you start today.

Once every box is checked, Step 331 is complete.