Reference exercises that accompany the HYF Data Track curriculum. Each week mirrors the chapters of the same week on Notion: Week 1 is Python foundations, Week 2 is structuring data pipelines, and so on.
Curriculum chapters link directly into specific exercise folders here. You don't need to clone anything to read the chapter — but to do the practice, open a Codespace (zero setup) or clone the repo locally.
A single Codespace covers every week's exercises:
The Codespace opens the repo root with Python 3.11 + Node.js LTS + VS Code extensions for both the Data Track (ruff, Pylance) and Core program (ESLint, Prettier) provisioned via .devcontainer/data-track/devcontainer.json. Navigate to data-track/week-N/exercise_X/ from the Explorer.
To clone instead:
git clone https://github.com/HackYourFuture/Learning-Resources.git
cd Learning-Resources/data-track| Week | Folder | Topic |
|---|---|---|
| 1 | week-1/ |
Python Foundations |
| 2 | week-2/ |
Structuring Data Pipelines |
| 3 onwards | (pending migration) |
Each week is a flat list of exercise_N/ folders. Each exercise carries its starter (exercise.py or similar) plus a solutions/ subfolder with the reference answer. The solutions/ folder is right next to the starter so you can diff against it cheaply once you have tried — but you have to deliberately open the folder, which is the spoiler barrier we want.
.devcontainer/
└── data-track/
└── devcontainer.json (Codespaces config: Python 3.11 + ruff + Pylance + debugpy)
data-track/
├── README.md (you are here)
├── week-1/
│ ├── README.md (Week 1 exercise overview)
│ ├── exercise_1/
│ │ ├── exercise.py
│ │ ├── README.md
│ │ └── solutions/
│ └── …
└── week-2/
└── …
The chapter you are reading on Notion will tell you to attempt an exercise on your own first. The solutions/ folder is the answer key: don't open it until you have tried. After your attempt, read the # WHY …: comments under each TODO before you read the code itself — the reasoning matters more than the syntax.