top of page

Terysa Ridgeway

Technology Leader at Google / Founder at Code+Play / Education & Training, STEM

Lafayette, Louisiana, USA / Hometown: Sunset, Louisiana / Black or African American

👩 she/her

🎓 B.S. Computer Science, Southern University

😁 She has four children, so her house is practically its own science experiment!

Terysa Ridgeway

Terysa founded Code+Play and wrote a children's book to help kids in rural Louisiana discover computer science through stories and play.

ABOUT HER WORK

Terysa Ridgeway is a technology leader at Google, children's book author, and founder of Code+Play, an interactive STEM learning experience that makes computer science fun and accessible for children. With a degree in Computer Science from Southern University and extensive experience in the technology industry, she is passionate about inspiring the next generation of innovators. Through storytelling, creative play, and hands-on learning, she helps children discover how coding and problem-solving can shape the world around them.

Terysa Ridgeway
Download poster

WATCH & DISCUSS

Watch: Introducing Terysa Ridgeway

Discuss:

  • How does Terysa use storytelling and play to help kids learn coding?

  • Where do you see problem-solving and computer science in your own home, school, or community?

EXTENSION ACTIVITIES

Suggested focus for grades 6–8: Story as Algorithm. In this unplugged activity, inspired by the hands-on, play-first approach of Code and Play, students write a short story as a set of precise instructions, then trade with a partner who “runs” the code exactly as written. Students learn sequencing, conditionals, loops, and debugging while discovering that coding and storytelling both depend on clear structure, careful word choice, and revision.


Lesson Plan: Story as Algorithm

Grades: 6–8
Time: Two 45-minute sessions
Materials: Index cards, sticky notes, chart paper, markers, a printed “Code Card” reference sheet

CS concepts: Algorithms, sequencing, conditionals (if/then), loops (repeat), debugging
ELA connections: Narrative structure, precise language, revision

Learning objectives: Students will

  • Write a short narrative as a step-by-step algorithm using sequence, a conditional, and a loop

  • Test and debug a partner’s story-algorithm

  • Explain how algorithms and stories both rely on structure and clear instructions

Session 1: Learn and Write

1. Hook (10 min): “Program the Teacher”
Students call out instructions for you to make a simple action happen, such as walking to the door and waving. Follow their words exactly (if they say “walk,” walk forever). Debrief: Why didn’t it work the first time? What makes an instruction clear?

2. Mini-lesson (10 min): Code Cards
Introduce four commands on a reference sheet:

  • DO — one action (DO: Character opens the door)

  • IF / THEN / ELSE — a choice (IF the dog barks, THEN run; ELSE tiptoe)

  • REPEAT ___ TIMES — a loop (REPEAT 3 TIMES: knock)

  • END — the story stops

Model a 6-line example story on chart paper.

3. Write (25 min)
In pairs, students write a story-algorithm of 8–12 lines, one command per index card. Requirements:

  • A clear beginning, middle, and end

  • At least one IF/THEN/ELSE

  • At least one REPEAT

  • One “variable” the reader chooses at the start (a name, a color, a weather condition) that changes the story

Session 2: Run, Debug, Reflect

4. Run the Code (15 min)
Pairs swap stories. One student reads the cards aloud like a computer; the partner acts them out or sketches each step exactly as written, no guessing. Each conditional gets tested both ways.

5. Debug (15 min)
Using sticky notes, the “computer” pair flags bugs: unclear steps, missing steps, loops that never end, or choices that lead nowhere. Original authors revise their cards.

6. Share and Reflect (15 min)
Two or three pairs perform their final stories. Discussion questions:

  • What was your trickiest bug, and how did you fix it?

  • How is debugging a program like revising a story?

  • Where do you see algorithms in everyday life?

Assessment

  • Checklist: Story includes sequence, a conditional, a loop, and a variable; it runs without errors after revision

  • Exit ticket: “Write one IF/THEN/ELSE that could change how your story ends.”

Differentiation

  • Support: Provide sentence frames and a partially written story to complete

  • Extend: Add nested conditionals, or translate the story into Scratch or another block-based language

  • Multilingual learners: Pair commands with icons; allow stories in home language

Extension

Groups combine their stories into a “choose your own path” class book, mapping all the branches on a large flowchart.

ADVICE TO YOUNGER SELF

​

Watch: Introducing Terysa Ridgeway

​

​

bottom of page