Last week produced clean aggregated reads. This week you do two things: shape the data into richer structures (group by source, dedup with sets, tagged matrices) and wrap each API call in try/except so a single failure returns a safe default instead of crashing the whole function.
Why introduce try/except in Week 2 instead of saving it for the end? The explorer track left it for later.
Because every lesson from Week 2 onward needs it. Once you're touching three APIs in one function, one of them will fail. A defensive wrapper keeps the other two working. Introducing it now means Weeks 3 and 4 can assume resilience as a given.
So I end the week able to combine three sources, dedup with sets, and absorb individual API failures without losing the whole result?
Exactly. That's the production skill that makes idempotent writes (Week 3) and full pipelines (Week 4) possible.
{source, content, id} matrix from three APIsGoal: Richer shapes plus resilient reads.
Create a free account to get started. Paid plans unlock all tracks.
Last week produced clean aggregated reads. This week you do two things: shape the data into richer structures (group by source, dedup with sets, tagged matrices) and wrap each API call in try/except so a single failure returns a safe default instead of crashing the whole function.
Why introduce try/except in Week 2 instead of saving it for the end? The explorer track left it for later.
Because every lesson from Week 2 onward needs it. Once you're touching three APIs in one function, one of them will fail. A defensive wrapper keeps the other two working. Introducing it now means Weeks 3 and 4 can assume resilience as a given.
So I end the week able to combine three sources, dedup with sets, and absorb individual API failures without losing the whole result?
Exactly. That's the production skill that makes idempotent writes (Week 3) and full pipelines (Week 4) possible.
{source, content, id} matrix from three APIsGoal: Richer shapes plus resilient reads.