Week 3 - Ingesting and Validating Data
Introduction to Data Ingestion
Assignment: Build a Validated Ingestion Pipeline
Going Further: Optional Deep Dives
History: APIs and Data Transfer
This page is optional. Nothing here is required for Week 3'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 3 starts mattering more in your day-to-day work.
Sections are grouped by topic: full courses and tutorials for the long-form route, deep dives on specific topics for going one layer below this week's chapters, declarative ingestion for the production frameworks (dlt, Airbyte, Meltano) that wrap the patterns you built by hand, videos for tangential talks, and community and books for the bigger picture.
<aside> 💡 Links that already appear inside a Week 3 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>
The chapters' Extra reading sections deliberately stay short. The big ones live here.
requests patterns of Ch2 further into auth, pagination, and rate-limit handling.One layer below what each chapter taught.
httpx: async HTTP client: the modern async alternative to requests. Same API shape, but lets you fetch from 50 APIs in parallel. Worth meeting once you have multiple ingestion sources.requests library deep dive: sessions, adapters, and urllib3.Retry. The chapter touched on requests; this is the rest.Week 3 builds an ingestion pipeline by hand on purpose: you need to feel the pain before you reach for the tools. In production, teams often hand the boilerplate to a declarative framework.
Tangential talks that do not belong inside a specific chapter's Extra reading.
with statement and context-manager pattern you used in Ch6 for database connections.Week 4 is Pandas for in-memory data processing; Week 5 hardens the pipeline shape; Week 6 is the first cloud-deployed pipeline on Azure. The ingestion habits you built this week (timeouts, retries, validation, idempotent writes) are the foundation every later week assumes you can write without thinking.
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.