Our Story
How We Built
Rally School
with AI
A father-and-son experiment in tennis, technology, and learning in the Generative AI era
🎾It started with time on the court, questions at home, and the belief that learning is better when we do it together.
The beginning
It Started with Tennis
Rally School did not begin as a software project. It began with tennis and a simple question:
“How can we make learning tennis easier for junior players and their parents?”
As Ethan developed as a junior tennis player, David and Ethan spent considerable time learning about tennis together: technique, practice, equipment, junior development, competition, the mental game, movement, and the many questions junior players and their parents encounter.
Ethan is a dedicated junior tennis player who also enjoys helping younger children learn the game. He has helped introduce younger children—including first-time players around ages 6–7—to simple activities and drills that help them learn the sport and build confidence.
That experience inspired another question:
“What if we could organize some of what we are learning into a simple online resource that could help other junior players and families?”
That idea became Rally School — Junior Tennis Fundamentals.
Start with why
We Didn't Start with Code
One of our biggest lessons was that an AI-assisted project does not need to begin with programming. We started with questions.
Who are we trying to help?
What problems do junior tennis parents encounter?
What does a first-time child actually need?
How should learning progress?
What information is genuinely useful?
What creates unnecessary complexity?
What should someone do next?
Real Experience→Questions→Ideas→Requirements→AI-Assisted Implementation→Testing→Improvement
The requirements came before the code.
Working together
Human Ideas + AI Implementation
David + EthanPeople
↓
Experience / Ideas / Feedback
↓
ChatGPTBrainstorm / Organize / Product Requirements
↓
CodexBuild / Modify Code
↓
Rally School
↓
David + Ethan ReviewFeedback → Improve → Repeat
“AI helped us build the website. It didn't decide why the website should exist.”
We still needed to define the problem.
Understand the users.
Decide what was important.
Provide clear requirements.
Review AI-generated work.
Test whether the site worked.
Identify errors or weak ideas.
Decide what to improve next.
The bigger lesson
Learning How to Learn
Traditionally, someone interested in technology might ask, “How do I code this?” That question remains useful. But more questions are becoming increasingly important.
What should I build?
Why should it exist?
Who does it help?
How do I explain the problem clearly?
How do I know whether AI's answer is correct?
What assumptions is AI making?
How can I improve the result?
These questions build curiosity, communication, critical thinking, judgment, creativity, experimentation, domain knowledge, and persistence.
Ethan's role
Junior Player → Contributor → Builder
Ethan was not simply the subject of the site. His experiences as a developing junior player helped shape the resource.
What junior players need
What beginners may find difficult
Which concepts need simple explanations
What practice activities feel engaging
How a junior can communicate tennis to younger children
His experience helping younger beginners also contributed to the Beginner Tennis Training section. Working on Rally School became a learning experience involving tennis, teaching, communication, product thinking, technology, and Generative AI.
Evidence over assumptions
AI Did Not Always Get It Right
Using AI did not mean every answer or code change was correct. We still had to investigate what was really happening.
Problem↓Observe↓Check the Actual Evidence↓Understand the Cause↓Make a Small Change↓Test Again
Local and hosted sites showed different versions.
Two similar GitHub repositories had to be distinguished.
We determined which repository powered rallyschoolonline.com.
Browser caching sometimes required a hard refresh.
GitHub Pages had to deploy the correct version.
YouTube IDs needed verification—not blind trust.
Embeds behaved differently locally and in production.
Checklist storage keys and JavaScript hooks needed protection.
AI suggestions still had to improve the real user experience.
Learning to debug AI-generated work was itself an important skill.
Different tools, connected work
ChatGPT vs Codex
AI did a large amount of the implementation work, but we still had to decide what to build, test whether it worked, identify problems, and decide what should happen next.
Where we are now
Still Learning
Rally School is not intended to replace tennis coaches, clubs, parents, or the experience of learning on the court.
It is a small project created by a father and son who enjoy tennis, technology, and learning together. Generative AI helped us turn ideas into something real much faster than would have been possible for us before.
But perhaps the most important lesson was not how much AI could do for us. It was realizing how much we still needed to learn ourselves.
For Ethan and other young people growing up in the Generative AI era, knowing today's technology will not be enough, because technology will continue changing. What may matter even more is curiosity to explore something new, the ability to ask good questions, judgment to evaluate answers, willingness to learn from mistakes, persistence to keep improving, and the ability to use powerful tools responsibly.
You do not become a better tennis player from one perfect swing.
You practice. You make mistakes. You understand them. You adjust. You try again.
Learning with AI can work the same way.
Keep playing. Keep building. Keep learning.
Built by David & Ethan for the junior tennis community.