What is sharing code online — explained for kids?

GitHub is where code lives and how developers collaborate. A first tour for young coders. For Class 7.

What's the most common mistake children make about this concept?

You need to be an experienced programmer to use Git and a code-sharing site — in reality, they are useful from day one (the site on a grown-up's account if you are under 13) as a place to save, share, and track learning

How does Dhee Learning teach this in a Class 7 session?

Dhee opens with a question — for example: "You have been saving your Python notebook in a cloud drive. Why might that be a problem if you want to share your work with someone else or come back to it in six months?" — listens to your child's answer, then probes the reasoning behind it. The session ends when the child can apply the idea to a brand-new situation, not just recall it.

What is GitHub? A gentle tour for beginners — Class 7

What this concept actually says

Git tracks changes to code; a code-sharing site keeps a copy online so developers can share and collaborate
A commit is a saved snapshot of your code with a message explaining what changed and why
A README is the front door of a repository — it tells the world what the project does and how to use it

An analogy your child will recognise

School science fair project journal

A science fair judge does not just look at your final poster — they want to see your lab notebook showing every experiment, failed attempt, and revision. Git is that lab notebook for code. Every commit is an entry: date, what you tried, what changed.

Building a house with an architect

An architect keeps every version of the blueprint — the initial sketch, the revision after the client changed their mind, the structural changes after the soil test. Git does the same for code. You never throw away an old version; you add a new one on top, with notes explaining why.

Common misconceptions to watch for

You need to be an experienced programmer to use Git and a code-sharing site — in reality, they are useful from day one (the site on a grown-up's account if you are under 13) as a place to save, share, and track learning
Deleting a file from a Git project deletes it permanently — in reality, if it was ever committed, it exists in the Git history and can be recovered

Key facts in one breath

The biggest code-sharing site hosts over 500 million repositories and is the largest platform for open-source software in the world
Git (the underlying tool) and a code-sharing site (the platform) are different: Git is the version control system; the code-sharing site is the cloud service that hosts Git repositories
A repository's README is written in Markdown — a simple formatting language that renders nicely on code-sharing sites
Public repositories are visible to everyone; private repositories are only accessible to invited collaborators — choose based on what you are sharing

How Dhee Learning teaches this — the 3-stage question loop

Every Dhee Learning session for this concept follows three stages. We share the questions Dhee actually asks, so you can hear what a session sounds like.

Stage 1 — Surface

You have been saving your Python notebook in a cloud drive. Why might that be a problem if you want to share your work with someone else or come back to it in six months?

Rote answer

"A code-sharing site stores your code online"

Understood

"A cloud drive's saved versions are unnamed and none carry a note about what changed, so months later you can't tell which one was the working version. Git keeps every version ever committed with a message about what changed, so you can see the full history of your thinking and revert to any earlier version."

Stage 2 — Reasoning

Why does a good commit message matter? Compare 'fixed stuff' to 'fix KeyError in data cleaning when income column has null values'. What information does the second one preserve that the first one loses?

Follow-up Dhee may use: If you are working on a team and someone writes 'updated file' as a commit message, what is the real cost to the team?

Stage 3 — Application

Without publishing anything, write a README for your AI project on paper or in a notebook text cell that explains what the project does, what data it uses, and what you found. Show me the README — does a stranger reading it know enough to understand your work? (Many code-sharing sites need you to be 13 or older, with one person per account, so a parent or teacher publishes it later from their own account.)

Misconception Dhee watches for: Treating Git and a code-sharing site as just a backup rather than a way to communicate and work together — the README and commit messages are as important as the code itself

Related concepts

Class 7

How to run an AI ethics review — fairness, privacy and harm