Fluency Class 1 — Personal Tech Journey

💬

Opening – Real-World Trigger

≈5-10 min • Natural conversation starter

🎯 Goal: Start with a real situation that triggers storytelling

Choose one trigger moment to share:

Option 1: "I just saw this junior developer's code review yesterday. They made the exact same mistakes I made when I started 7 years ago—hard-coding everything, zero error handling. It got me thinking about my own first programming experience..."

Option 2: "My friend asked me yesterday why I chose tech as a career. I realized I've never really told the full story of how I got into this. It's kind of wild when I think about it..."

Option 3: "I was cleaning out old files and found my first website from 2012. The code is absolutely terrible! But it reminded me of that moment when I first discovered I could build things with code..."

Then naturally ask: "What about you? Do you remember your first time touching code?"

💡 Important: This isn't a Q&A session—it's a real conversation. Share your authentic trigger moment first (2-3 minutes) to model natural storytelling. Then let the conversation flow naturally. Don't force through all questions if the conversation goes elsewhere.

🛠️ Conversation Toolkit: Emergency Starters

If the conversation stalls or answers are very short:

"Walk me through that moment. Where were you physically when it happened?"
"That's interesting! What made you decide to keep going after that?"
"I had a similar experience with [related topic]. Did you feel [emotion] too?"

📚

Vocabulary Bank – Learn Through Dialogue

≈8-12 min • Natural phrase introduction

📖 Essential Storytelling Phrases

Introduce these phrases through a complete dialogue, then practice:

Complete Example Dialogue:

Teacher: "So I got into programming back in 2010. I was trying to customize my blog and realized I could actually change the code."

Student: "Oh, I also got into it because of a website. Mine was in 2015."

Teacher: "Nice! Did you find it easy at the start, or did you struggle with anything?"

Student: "I definitely struggled with understanding how JavaScript worked. I felt totally overwhelmed by all the syntax."

Teacher: "That's so normal! It took me a while to understand async functions. But then I had this breakthrough when I finally understood promises."

Student: "Same! My breakthrough was when loops finally clicked for me."

Teacher: "Looking back, those struggles actually taught me patience. What would you tell your past self?"

Phrase	Natural Usage in Conversation
get into	"I got into programming when..." / "How did you get into this field?"
struggle with	"I struggled with understanding X" / "Did you struggle with that too?"
overwhelmed	"I felt completely overwhelmed by..." / "Were you overwhelmed at first?"
breakthrough	"I had a breakthrough when..." / "What was your first breakthrough moment?"
looking back	"Looking back, I should have..." / "Looking back, what would you change?"
it took me a while to	"It took me a while to understand X" / "Did it take you long to learn Y?"

🎯 Quick Practice: Complete the Story

Complete this coding story with the vocabulary words:

got into

struggle

overwhelmed

Looking back

It took me a while to

breakthrough

I programming when I was 15 years old. At first, I felt by all the concepts I needed to learn. I really with understanding loops and functions. , I realize that everyone faces these challenges when starting. write my first working program without bugs. But then I had a major when recursion finally made sense to me!

🎭

Practice Scenarios – Vocabulary in Context

≈8-12 min • Professional situations

🎯 Use the vocabulary in real professional contexts

Choose 2-3 scenarios based on student interest and energy level. Alternate roles with your teacher!

Scenario 1: Mentoring a Struggling Junior Developer

Context: A junior dev on your team just messaged you: "I feel so lost with async/await. Maybe I'm not cut out for this." You want to share your own journey to help them.

Example opening: "Hey, I totally get it. When I first got into programming, I also struggled with async concepts. I remember feeling completely overwhelmed..."

Practice: Have a 2-3 minute supportive conversation using today's phrases naturally

Scenario 2: Technical Interview - "Tell Me About Yourself"

Context: You're in a job interview. The interviewer asks: "Walk me through how you became a developer and what motivates you in this field."

Example structure: "I got into programming [when/how]. Initially I struggled with [concept], but I had a breakthrough when [specific moment]..."

Practice: Give a professional 2-minute answer, then teacher asks follow-up questions

Scenario 3: Networking at a Tech Conference

Context: Someone at a meetup asks casually: "So how did you end up in tech?" You want to give an interesting but concise version of your story.

Practice: Natural 1-2 minute conversation mixing all vocabulary phrases

🛠️ Facilitation Toolkit: Energy Adjustments

If energy is low: Do Scenario 3 (shortest), make it fun and casual
If highly engaged: Do all three scenarios, add follow-up questions
If struggling with vocabulary: Model the phrase first, then try again

🎤

Main Conversation – Your Complete Tech Journey

≈20-30 min • Interactive storytelling (podcast style)

🎯 Tell Your Coding Origin Story

This should feel like a podcast interview, not a formal presentation. One person tells their story naturally while the other asks genuine questions throughout.

Choose Your Pathway Based on Confidence Level:

🟢 Path A: Confident & Talkative

Tell the story with minimal interruptions (10-15 min), then respond to deeper questions (10-15 min). Focus on adding nuance and professional depth.

Follow-up questions: "What would you have done differently?" / "How did that experience shape how you approach [specific situation] now?"

🟡 Path B: Needs Support

Use guiding questions throughout to build the story collaboratively. More back-and-forth conversation (alternate naturally).

Guiding approach: Ask specific questions like "What happened next?" / "How did you feel when that happened?" / Share similar experiences to model storytelling

🔵 Path C: Advanced (Add Challenge)

After the basic story, explore stakeholder perspectives to deepen critical thinking.

Challenge questions: "Based on your experience, what advice would you give to someone hiring junior developers?" / "If you were designing a coding bootcamp based on your journey, what would you prioritize?"

Story Structure Guidance (for all paths):

The Beginning: How and when you discovered programming (context matters—where were you, what triggered it?)
First Challenges: Specific struggles you faced and honest emotions (not just "it was hard")
First Real Project: What you built, what went wrong, what you learned
Breakthrough Moment: When things started clicking (what specifically changed?)
Evolution to Now: How you've grown from beginner to current level
Reflection: What you'd tell your past self / What this journey taught you beyond code

🎙️ How This Works (for all paths):

Storyteller: Tells story naturally (NOT reading notes—speak from memory and emotion)

Listener: Asks genuine questions when curious:

"Wait, how old were you when that happened?"

"That must have been frustrating! What made you keep going?"

"I had a similar experience with [topic]. Did you feel the same way?"

"Walk me through exactly what happened next..."

"What was running through your mind at that moment?"

🛠️ Facilitation Toolkit: Deepening Techniques

If story is too surface-level: "Tell me more about that specific moment" / "What exactly did you do?"
If rushing through important parts: "Hold on, that sounds important. Let's unpack that a bit more."
To add professional depth: "How does that experience influence your work now?" / "What did that teach you about [learning/problem-solving/persistence]?"
If stuck: Share your own related experience first to model, then ask again

💡

Reflection & Real-World Application

≈5-8 min • Connect to actual work

🎯 Connect today's class to real professional situations:

Discuss naturally (not all questions, just what feels relevant):

Which phrase from today will you actually use in your work this week?
If you had a job interview tomorrow and they asked "Tell me about yourself," how would you start?
Do you have any team members who might benefit from hearing your story? Why?
What surprised you about telling your story in English today?

💼 Real-world application: These phrases aren't just for English class. You'll use them in job interviews, 1-on-1s with your manager, team introductions, conference networking, mentoring juniors, and LinkedIn posts. This is professional storytelling.

🎯

Homework – Real-World Practice

Choose one actionable task

📝 Apply Your Story to Your Actual Career

Choose ONE option that fits your current situation:

Option 1: Update Your LinkedIn About Section

Rewrite your LinkedIn "About" section using 3-4 phrases from today. Make it tell your authentic coding journey story. (150-200 words)

Option 2: Prepare for Your Next 1-on-1 with Your Manager

Write 3-4 bullet points about your growth journey that you could mention in your next 1-on-1. Use today's vocabulary to express challenges you've overcome.

Option 3: Record Your "Interview Answer"

Record yourself (audio or video, 3-5 min) answering: "Tell me about how you became a developer and what keeps you motivated." Listen back and note 2-3 areas to improve fluency.

Option 4: Write a Message to a Junior Developer

Draft a message (150-200 words) you could send to a struggling junior developer on your team, sharing your own journey and encouragement. Use at least 4 phrases from today.

Quality Checklist:

At least 4 vocabulary phrases from today's class used naturally
Specific examples and details (not generic statements like "I learned a lot")
Your authentic voice and personality showing through
Something you could actually use in your real professional life this week

🚀 Fluency Class 1 – Personal Tech Journey