How much does zuzu.codes cost?

The starter track is free — read all lessons and practice for free. Full access to every track (current and future) is $14.99/month. Cancel anytime.

How long does each track take?

Each track is designed as a 30-day challenge — one lesson per day, about 15 minutes each. Go at your own pace, but the structure is built around daily consistency.

What's the lesson format?

Each lesson is a student-teacher dialogue with code examples, followed by a hands-on code challenge in an in-browser editor. You read, you understand, then you write real code.

Do I need prior coding experience?

Our beginner track starts from absolute zero — no prior experience needed. Advanced tracks build on earlier ones, and the platform tells you exactly where to start.

How is zuzu.codes different from freeCodeCamp or Codecademy?

zuzu.codes uses a structured 30-day track format with dialogue-based teaching, an in-browser code editor, and gamification (XP, streaks, progress tracking). The format builds genuine understanding through daily practice.

Day 9 · ~11 min●

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.

This Week

Day 10 — dedup titles across Gmail, Calendar, and Tasks using sets
Day 11 — group a combined list back into per-source buckets
Day 12 — build a tagged {source, content, id} matrix from three APIs
Day 13 — try/except around one API call, return a safe default
Day 14 — try/except per API, combine only what succeeded

Goal: Richer shapes plus resilient reads.

Sign up to practice

Create a free account to get started. Paid plans unlock all tracks.

Day 9 · ~11 min●

Why introduce try/except in Week 2 instead of saving it for the end? The explorer track left it for later.

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.

This Week

Day 10 — dedup titles across Gmail, Calendar, and Tasks using sets
Day 11 — group a combined list back into per-source buckets
Day 12 — build a tagged {source, content, id} matrix from three APIs
Day 13 — try/except around one API call, return a safe default
Day 14 — try/except per API, combine only what succeeded

Goal: Richer shapes plus resilient reads.

This Week

Day 10 — dedup titles across Gmail, Calendar, and Tasks using sets

Day 11 — group a combined list back into per-source buckets

Day 12 — build a tagged {source, content, id} matrix from three APIs

Day 13 — try/except around one API call, return a safe default

Day 14 — try/except per API, combine only what succeeded

Goal: Richer shapes plus resilient reads.

This Week

Day 10 — dedup titles across Gmail, Calendar, and Tasks using sets

Day 11 — group a combined list back into per-source buckets

Day 12 — build a tagged {source, content, id} matrix from three APIs

Day 13 — try/except around one API call, return a safe default

Day 14 — try/except per API, combine only what succeeded

Goal: Richer shapes plus resilient reads.