Training 28 July

Main ideas, concepts, and lessons

1) Purpose of the weekly training

• The event depends on everyone’s participation to run smoothly.
• The group holds weekly Friday trainings to:
  • Learn how to solve current teaching problems.
  • Improve learning/coding teaching practices (with additional trainings still planned).
  • Align everyone’s understanding of what coding teaching should look like.
  • Share experiences and solve problems together in a forum (weekly meetups).

2) Problems observed in coding/tutoring classes

Speakers discuss recurring issues, including:

1. Low student interaction

   • Classes can become “one-way” (students mainly watch/receive explanation).
   • Example pattern: students listen to presentations/reminders, then practice, but interaction remains limited.
   • Challenge: make classes more lively and interactive.

2. Poor time management

   • Tutorials often exceed the target duration (e.g., should be 1 hour but becomes 1.5 hours).
   • Consequence mentioned: impacts effectiveness and income generation.

3. Students feel overwhelmed by complex material

   • Some students struggle with dense/advanced content, especially when explanations and pacing are not adjusted.

3) General solutions/methods proposed (step-by-step and in bullets)

A. Make learning more interactive (visual/online tools + engagement)

• Use Zoom-based interaction features, such as:
  • Annotations/highlighting important points
  • Visual emphasis on key parts during explanation
• Goal: create visual interaction and increase involvement.

B. Build fun and structured sessions

• Add ice breakers/games (especially earlier in the class) to keep students engaged.

C. Improve time management with a “percentage mix” approach

A concrete pacing methodology is proposed:

• Use a mix similar to:
  • 30% theory (short explanation)
  • 60% practice (students doing tasks)
  • 10% ice breaker/game

Key guidance:

• Don’t spend too long explaining slides—if the PPT is full (e.g., 40–60 slides), students get bored and practice time disappears.

Practical suggestion:

• Use a timer to monitor time remaining.
• If time is near over, shift to practice or move on to the next segment rather than expanding explanations.

D. When explaining concepts: prioritize understanding, not slide-by-slide coverage

Prioritize:

• Understanding the concept
• Using everyday-life examples

Avoid:

• Rushing students who don’t understand
• Forcing all slide content if it exceeds students’ capacity

Adjust PPT content:

• Use only parts that match students’ level.
• Skip or shorten the rest.

---

Detailed instructions and strategies shared by speakers (by topic)

Speaker: Monika (coding teaching + time management + platform & parental direction)

Time management / class delivery

• In the first meeting, learn:
  • Student abilities
  • Student interests
• Show platform usage in the first lesson (e.g., Scratch: choosing background/characters; finding where assignments are).
• Prevent common time-wasters:
  • Don’t explain assignment navigation one-by-one; demonstrate clearly and point students to where tasks are.
• While students work:
  • Ask students to share screens, especially those who are lacking or not engaging (e.g., not opening camera).
• Adjust ice breakers based on task difficulty:
  • If tasks are easy → include more ice breaker/game time.
  • If tasks are difficult → shorten games; reduce transitions that waste time.

Expectation handling

• Monitor work speed and adjust:
  • If most can finish quickly → add “bonus tasks” to keep them engaged.
  • Never remove motivation by saying bonus is optional.

Pacing strategy while presenting

• Don’t explain every PPT detail.
• Teach the concept first, then go straight to assignment practice.
• Rarely rely on additional external applications; use platform tools and minimal additions to boost interest.

Platform involvement / “Infolping”

• Introduce and encourage use of platform features:
  • Laboratory room: feel “special,” private space to explore without fear.
  • Community: inspiration via others’ projects; engagement via comments/interaction.
  • Missions/goals: remind every couple of meetings; rewards boost confidence.
  • Encourage exploring similar works and external ideas when needed.

Parents/“How to involve kids outside the session”

• For parent sessions:
  • Invite kids to show results.
  • Encourage children to try making their own projects and referencing the community/library for ideas.

---

Speaker: Erin (tutoring management + informing kids/parents about the platform)

Tutor time management

• Start on time with strict discipline:
  • Start within a small tolerance window; otherwise begin regardless of late students.
  • Don’t wait for undisciplined students to respect those who arrived.
• Finish according to schedule:
  • Stop when time is up.
  • Provide extra only if necessary (rare extension / communicate with parents for follow-up).

Reminders and appreciation

• Send reminders to all student groups on the same day:
  • Announce that parents should join / students should come.
  • Mention which students joined to reinforce positive behavior.
• Handle lateness:
  • Reprimand repeated late attendance.
  • Allow lateness only with prior notice; otherwise class may proceed.
  • Establish agreements for students who may skip/late.

Get to know students + handle special needs

• Monitor special circumstances (e.g., students who can’t do tasks alone).
• Communicate honestly with parents:
  • If group pace prevents progress, suggest moving to private classes to prevent delay and improve learning outcomes.

Platform informing (“Infolping”)

• Define what students can do beyond lessons:
  • Community, games, laboratory/projects.
• Build loyalty/engagement through:
  • Initial platform introduction/demo
  • Encouraging play in community during free time
  • Having finished students create their own projects outside class
  • “Show-off” sessions where children share projects with peers
  • Teaching them to inspect code inside examples (copy/follow) as a learning skill

---

Speaker: Winda (management + review strategy)

Time management

• Mistake to avoid: class running late.
• Strategy that helped:
  • Announce remaining time
  • Use the clock so students understand boundaries and finish on schedule.

Review strategy problems & solutions

• Review can fail when:
  • Students can’t remember or claim they forgot previous material.
• Approach:
  • Determine what students already understand vs. what they don’t.
  • Skip review parts that are already understood.
• Encourage “discovery” over memorization:
  • Instead of demanding memorized answers, ask students to find answers.
• Resource-based mindset:
  • Searching/opening Google is considered unavoidable in coding/review; guide it rather than treat it as failure.

---

Speaker: Mas Anas / Galang / others (additional frameworks for platform use + time management)

Time management framework (4 points)

1. Profiling in the initial meeting
   • Learn shortcomings, potential, and interests
   • Build bonding first (ask background, hobbies)
   • Record notes about the child
2. Advance reminders
   • Reminder to join before class starts; allow questions/support
3. Know the material
   • Understand learning goals and approximate pacing (use benchmarks if available, but not rigidly)
4. Know the students’ needs
   • Adjust to interests and needs without deviating from curriculum

Platform feature strategies

• Maximize:
  • Laboratory (private “special room”)
  • Community page (inspiration, engagement)
  • Missions/rewards reminders every 2 meetings
  • Exploration of works to keep students engaged

---

Q&A themes (common practical dilemmas and responses)

Handling dense material vs time limits (especially PS/Python/VP tracks)

• Advice given:
  • Don’t overload PPT explanation.
  • Use PPT as illustration only.
  • Go directly to the problem section/exercises and let students practice while the tutor helps.

If one child is slow and blocks the group pace

• Guidance:
  • If possible, move the child to private for better pacing and to avoid delaying the rest.
  • Tutors may “work around it” in group by adjusting how/when they help.

Different age groups: younger vs older student atmosphere

• Observations:
  • Ages ~7–9 are more enthusiastic.
  • Ages 10–12 may be quieter/less engaged.
• Possible explanation:
  • Older students may feel less comfortable (similar to junior-high), and may not want to socialize as much.
• System note mentioned: track/class division changed:
  • CK starts around 5–6
  • 7–11 is VP
  • Python starts around 11–17 (age split adjusted)

Teaching Python to students with no coding background

• Recommended approach:
  • Confirm proper track placement using trial/observation.
  • If Python is too hard due to missing foundation, strengthen fundamentals via VP/earlier modules first, then return to Python.

Combat Code / learning style mismatch

• Combat Code (Python-class approach):
  • Prefer interactive game-like navigation; PPT becomes supporting material.
  • Use code directly on the platform with an “adventure”/game context at the start.

---

Speakers/sources featured (identified from subtitles)

1. Speaker 1 (unnamed in subtitle header; main early presentation): “Monika” (referred to as Kak Monica)
2. Erin (Kak Erin)
3. Monika (Kak Monica — explicitly named later as “Thank you… Monica”)
4. Winda (Kak Winda)
5. Mas Anas / Mas Ales / Mas Galang / Mas Nadif / Mas Purwanto / Mas Kevin / Mas Fikri / Mas Ali / Mas Nadif (mentioned across Q&A; some also referred to as tutors/senior tutors)
6. Kak Adinda (participant in Q&A)
7. Royan / Reza / Fikri / Kevin / Galang (participants referenced in Q&A)
8. Sis Erin (same as Erin, mentioned informally in the first segment)