Azure Setup and Account Access
Week 1 Assignment: The Data Cleaning Pipeline
Going Further: Optional Deep Dives
This page is optional. Nothing here is required for Week 1's learning goals or the assignment. Use it after you finish the week if you want to keep learning, or come back later when a specific topic from Week 1 starts mattering more in your day-to-day work.
Sections are grouped by topic: deeper-but-still-Week-1 videos (Corey Schafer's longer takes on the chapters' concepts), full courses and books (the long-form route), setup and tooling beyond the basics (the next layer above venv + pip), cloud orientation (Azure context for the Week 6 ramp), and career and community (orientation to the Dutch data-engineering job market).
<aside> 💡 Links that already appear inside a Week 1 chapter's Extra reading section are not duplicated here. This page is the home for resources that are too broad to fit any single chapter, or that go meaningfully deeper than the chapter's tightly-scoped reading.
</aside>
Corey Schafer's tutorials are the standard recommendation across the Python community. Each runs 10-30 minutes and goes meaningfully deeper than the matching Week 1 chapter.
break, continue. Pairs with Ch3 if the docs reference felt thin.import statements, sys.path, picking the right standard-library module. Pairs with Ch4.typing module beyond the PEP 484 basics. Pairs with Ch5.else/finally clauses. Pairs with Ch7.with open(...), modes, and chunking large files. Pairs with Ch9.The chapters' Extra reading sections deliberately stay short (2-4 links each, no multi-hour resources). The big ones live here.
Week 1 sets you up with venv and pip. The Python tooling ecosystem has grown several layers since those were the standard.
uv: modern Rust-based replacement for pip + venv + pip-tools, ~10-100× faster. Drop-in replacement for most flows. Worth meeting now since the rest of the track uses it under the hood (the repo's own dependency management is already on uv).pyenv: manages multiple Python versions on one machine. Useful when one project needs 3.10 and another needs 3.12.flake8, isort, and (optionally) black in one tool. Week 5 will likely standardise on it for CI.requirements.txt stops being enough (per-project lockfiles, publishing your own packages).Week 1 Ch10 only verifies your Azure access. The actual cloud work starts in Week 6. If you want to start orienting earlier:
The track works toward a junior data-engineering job. Some context for the Dutch market:
After Week 1 you move into structuring data pipelines (Week 2), ingesting from real sources (Week 3), and processing with Pandas (Week 4). The Python skills you just built become tooling, not the focus. If you want a sneak preview:
csv module: Week 3 will lean on this heavily.The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*

Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.