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 15 · ~11 min●

This week moved from flat aggregation to richer shapes: sets for dedup, a dict-keyed-by-source grouping, a tagged matrix, and per-API try/except. How is the data modeling feeling?

Picking the right shape per problem is the hard part. Flat list when downstream is uniform, dict-of-lists when branching by source matters, tagged matrix when both are needed.

Exactly — the quiz tests that decision. Plus the try/except discipline: when to catch broadly, when to use a sentinel value, why per-API isolation matters.

The sentinel-vs-zero question — I want to make sure I nail it.

Think about what distinguishes 'no data' from 'fetch failed' — the answer follows.

Week 2 Recap

Five functions moving from pure aggregation to production-shaped resilience:

dedup_across_sources — set for membership, list for order
group_by_source — dict of lists keyed by gmail, calendar, tasks
build_source_matrix — list of {source, content, id} rows
safe_fetch_with_default — try/except with configurable fallback
safe_multi_source_counts — per-API try/except, -1 sentinel per failed source

Key idea: wrap API calls in try/except so one failure doesn't cascade.

Sign up to practice

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

Day 15 · ~11 min●

This week moved from flat aggregation to richer shapes: sets for dedup, a dict-keyed-by-source grouping, a tagged matrix, and per-API try/except. How is the data modeling feeling?

Picking the right shape per problem is the hard part. Flat list when downstream is uniform, dict-of-lists when branching by source matters, tagged matrix when both are needed.

Exactly — the quiz tests that decision. Plus the try/except discipline: when to catch broadly, when to use a sentinel value, why per-API isolation matters.

The sentinel-vs-zero question — I want to make sure I nail it.

Think about what distinguishes 'no data' from 'fetch failed' — the answer follows.

Week 2 Recap

Five functions moving from pure aggregation to production-shaped resilience:

dedup_across_sources — set for membership, list for order
group_by_source — dict of lists keyed by gmail, calendar, tasks
build_source_matrix — list of {source, content, id} rows
safe_fetch_with_default — try/except with configurable fallback
safe_multi_source_counts — per-API try/except, -1 sentinel per failed source

Key idea: wrap API calls in try/except so one failure doesn't cascade.

Week 2 Recap

Five functions moving from pure aggregation to production-shaped resilience:

dedup_across_sources — set for membership, list for order

group_by_source — dict of lists keyed by gmail, calendar, tasks

build_source_matrix — list of {source, content, id} rows

safe_fetch_with_default — try/except with configurable fallback

safe_multi_source_counts — per-API try/except, -1 sentinel per failed source

Key idea: wrap API calls in try/except so one failure doesn't cascade.

Week 2 Recap

Five functions moving from pure aggregation to production-shaped resilience:

dedup_across_sources — set for membership, list for order

group_by_source — dict of lists keyed by gmail, calendar, tasks

build_source_matrix — list of {source, content, id} rows

safe_fetch_with_default — try/except with configurable fallback

safe_multi_source_counts — per-API try/except, -1 sentinel per failed source

Key idea: wrap API calls in try/except so one failure doesn't cascade.