9. Where Git goes next

At a glance

Time: 3 periods · Tiers: 0–3 · You need: the pathway map template; optionally a guest speaker

Before this: the whole book.

By the end you can: explain where version control is used beyond school, and write a concrete plan for your own next steps.

Hook (5 min)

Most people learn Git as an "extra". You have now studied it for five years. Where does it actually take you — and what do you do on Monday?

Understand it

Where version control appears

Field	How Git is used	What you already know from this book
University (CS/IT/engineering)	assignments and labs submitted as repos; team projects; GitHub Classroom	Grades 9–12
Software and DevOps	PRs and code review, CI/CD, releases, infrastructure as code (servers described in files, changed by PR)	G10, G12 M2–M4
Research and science	reproducible analyses: code, data and paper versioned together; citations of software	G11 M8, G12 M8
Writing and documentation	docs-as-code: Markdown in Git, reviewed by PR, published by CI — like this book	G10 M7
Data and machine learning	versioned datasets and experiments (Git + LFS/DVC)	G11 M8
Design and games	asset versioning with Git LFS	— (see Version control in any project)
Government and civic tech	open data and open-source tools; transparent changes	G11 M1, M8
Open source	contribution, maintenance, mentoring programmes	G11

Skills that transfer

Even outside software, the habits matter: small steps with clear explanations, keeping history honest, reviewing others' work kindly, automating checks, documenting for strangers, and crediting sources.

Open-source programmes

Mentoring programmes such as Google Summer of Code and Outreachy pay contributors to work with open-source projects. Both require applicants to be 18 or older (checked October 2026; GSoC also requires student or open-source-beginner status), so many Grade 12 students become eligible only after school. Rules change every year — check the official pages yourself. Until then: contribute to welcoming projects, join local communities, and keep a portfolio.

Local communities (example: Nepal)

Local open-source and open-data communities (for example FOSS Nepal, NOSK, Open Knowledge Nepal, Code for Nepal) run events and projects. This book has not yet contacted them; check their current activities yourself.

Keep learning

Part VIII of this book (Version control in any project) shows how to bring Git into any project; Part IX lists books and free courses for the next level. A good next step for most students: MIT's Missing Semester lectures, the Pro Git book chapters you haven't read, and one real contribution per term.

See it

A completed pathway map (example):

Stage	Study	Work	Open source	Next concrete step
Now (Grade 12)	finish capstone v1.0.0	—	2 merged PRs to this book	add glossary words in your language (issue #41) by Poush
Next year	BSc CSIT entrance prep; Git for all assignments	—	translate one First Contributions page	read Pro Git ch. 7
After school	team projects at university	internship using code review	apply to a mentoring programme once eligible (18+)	keep CONTRIBUTIONS.md updated

Activity: talks and interview (40 min)

Interview an adult who uses version control (teacher, alumnus, parent) or watch a recorded talk. Guest-talk template: 5 min what I do · 5 min a story where history saved me · 10 min Q&A. Students prepare three questions in advance, e.g. "What did you wish you had learned at school?", "How does your team review work?", "What happens when something breaks?".

PRIMM lab

1. Interview / talk (above), or read about a field in the table and find one real example online.
2. Predict which of your interests connect to Git.
3. Fill the pathway map: now → next year → after school, with one concrete step each.
4. Investigate: find one open-source or open-data project related to your interest; apply the Grade 11 Module 2 reading strategy for 20 minutes.
5. Make: publish your map in your portfolio repo, alongside CONTRIBUTIONS.md and BADGES.md.

Parsons practice

Match field → Git use: research → reproducibility; industry → CI/CD; writing → documentation as code; data → versioned datasets.

Common mistakes

Mistake	Better
"Git is only for programmers"	writers, scientists, designers and governments use it
A plan without concrete steps	one action with a date per row
Waiting for a programme to start contributing	contribute now; programmes come later
Trusting old eligibility rules	check official pages every year

Practise more with free resources

#	Exercise	Tier	Time	Hand in
1	MIT Missing Semester — watch one lecture outside Git (e.g. Shell Tools).	3	60 min	5 things learned
2	The Turing Way — how researchers use version control.	3	30 min	summary
3	Open Source Guides — read one guide you haven't read.	3	20 min	summary
4	Choose one book from Part IX (Books and reading) to read this year; write why.	0	10 min	choice + reason

Exit ticket

1. Name two fields where Git is used.
2. What is your next concrete step?
3. Misconception: "Git is only for programmers."

Key points

• Version control is used in study, software, research, writing, data, design, government and open source.
• The habits transfer: small explained steps, honest history, kind review, automation, documentation, credit.
• Programmes have age and eligibility rules — check yearly; contribute now.
• A pathway map turns interest into a dated next step.

---

Book complete — for the grades. Continue with Part VII (After Grade 12: the foundation, consolidated) and Part VIII (Version control in any project).

Teacher notes

• Timing: P1: hook + understand 30, prepare questions 10. P2: talk/interview 40. P3: lab 30, exit 10.
• Re-check programme eligibility and dates the same week you teach this. Do not promise admissions or jobs. The GitHub Student Developer Pack was not checked.
• Invite alumni from Grade 12 capstones in earlier years once the curriculum has run.