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.

Synthesis — Automation Foundations

Day 21 · ~11 min●

Twenty lessons. Today you stitch four of them together on a tiny generic input. No new APIs.

Given an in-memory list of three IDs ["a", "b", "c"] and a values dict {"a": 5, "b": 15, "c": 20}:

For each ID, look up its value in the dict.
If the value > 10, create a Calendar event with summary "alert: <id>=<value>".
Print step logs.

Expected output: alerts fire for b (15) and c (20). a (5) is below threshold, skipped.

python

values_by_id = {"a": 5, "b": 15, "c": 20}
threshold = 10
ids = ["a", "b", "c"]

print("step 1: walking ids")
sent = 0
for item_id in ids:
    value = values_by_id.get(item_id, 0)
    if value > threshold:
        print(f"step 2: {item_id}={value} above threshold, alerting")
        toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
            "calendar_id": "primary",
            "summary": f"alert: {item_id}={value}",
            "start_datetime": "2026-12-31T11:00:00+00:00",
            "event_duration_minutes": 15,
        })
        sent += 1
print(f"step 3: sent {sent} alerts")

No new concepts at all?

Zero. Look-up (week 1 dicts), if-on-condition (week 2), side-effect call (week 9), step logging (yesterday). The whole-week skill: assemble these without overthinking.

What this synthesis composes

Primitive	From	Used for
Dict lookup with `.get(key, default)`	Auto-Beg L3 (and Py-Beg L15)	reading the value for each ID
`if value > threshold`	Py-Beg L8	the filter condition
`toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {...})`	Auto-Beg L10	the side effect
`print("step N: ...")`	Auto-Beg L20	step logging
Counter pattern (`sent += 1`)	Auto-Beg L17	report what fired

No new concepts. The hardest line is the f"alert: {item_id}={value}" interpolation — week 1 of Python Beginner.

What this synthesis does NOT compose

Deliberately not in scope for an Auto-Beg synthesis:

Real-time streaming of incoming messages
Multiple sequential side effects per item
Persistent state across runs (the scaffold uses an in-memory values_by_id, not a Sheet)
Retry on transient API failure

Those are Auto Intermediate. The skill of week 3 is recognizing a 4-primitive shape and writing it cleanly — not trying to anticipate every edge case.

The right shape, the wrong shape, the over-shape

python

# right — lean, four primitives, clear
for item_id in ids:
    value = values_by_id.get(item_id, 0)
    if value > threshold:
        side_effect(item_id, value)
        sent += 1

# wrong — assumes every key is present
for item_id in ids:
    value = values_by_id[item_id]    # KeyError if missing

# over-shape — too defensive for a 3-item synthesis
try:
    for item_id in ids:
        try:
            value = values_by_id.get(item_id, 0)
            ...
        except Exception as e:
            print(f"item {item_id} failed: {e}")
except Exception as e:
    print(f"outer failed: {e}")

Match the defensiveness to the lesson. For day 19's purpose-built error-chain lesson, the over-shape is right. For today's synthesis, the lean shape is right.

Day 21 · ~11 min●

Twenty lessons. Today you stitch four of them together on a tiny generic input. No new APIs.

Given an in-memory list of three IDs ["a", "b", "c"] and a values dict {"a": 5, "b": 15, "c": 20}:

For each ID, look up its value in the dict.
If the value > 10, create a Calendar event with summary "alert: <id>=<value>".
Print step logs.

Expected output: alerts fire for b (15) and c (20). a (5) is below threshold, skipped.

python

values_by_id = {"a": 5, "b": 15, "c": 20}
threshold = 10
ids = ["a", "b", "c"]

print("step 1: walking ids")
sent = 0
for item_id in ids:
    value = values_by_id.get(item_id, 0)
    if value > threshold:
        print(f"step 2: {item_id}={value} above threshold, alerting")
        toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
            "calendar_id": "primary",
            "summary": f"alert: {item_id}={value}",
            "start_datetime": "2026-12-31T11:00:00+00:00",
            "event_duration_minutes": 15,
        })
        sent += 1
print(f"step 3: sent {sent} alerts")

No new concepts at all?

Zero. Look-up (week 1 dicts), if-on-condition (week 2), side-effect call (week 9), step logging (yesterday). The whole-week skill: assemble these without overthinking.

What this synthesis composes

Primitive	From	Used for
Dict lookup with `.get(key, default)`	Auto-Beg L3 (and Py-Beg L15)	reading the value for each ID
`if value > threshold`	Py-Beg L8	the filter condition
`toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {...})`	Auto-Beg L10	the side effect
`print("step N: ...")`	Auto-Beg L20	step logging
Counter pattern (`sent += 1`)	Auto-Beg L17	report what fired

No new concepts. The hardest line is the f"alert: {item_id}={value}" interpolation — week 1 of Python Beginner.

What this synthesis does NOT compose

Deliberately not in scope for an Auto-Beg synthesis:

Real-time streaming of incoming messages
Multiple sequential side effects per item
Persistent state across runs (the scaffold uses an in-memory values_by_id, not a Sheet)
Retry on transient API failure

Those are Auto Intermediate. The skill of week 3 is recognizing a 4-primitive shape and writing it cleanly — not trying to anticipate every edge case.

The right shape, the wrong shape, the over-shape

python

# right — lean, four primitives, clear
for item_id in ids:
    value = values_by_id.get(item_id, 0)
    if value > threshold:
        side_effect(item_id, value)
        sent += 1

# wrong — assumes every key is present
for item_id in ids:
    value = values_by_id[item_id]    # KeyError if missing

# over-shape — too defensive for a 3-item synthesis
try:
    for item_id in ids:
        try:
            value = values_by_id.get(item_id, 0)
            ...
        except Exception as e:
            print(f"item {item_id} failed: {e}")
except Exception as e:
    print(f"outer failed: {e}")

Match the defensiveness to the lesson. For day 19's purpose-built error-chain lesson, the over-shape is right. For today's synthesis, the lean shape is right.

What this synthesis composes

What this synthesis does NOT compose

The right shape, the wrong shape, the over-shape

What this synthesis composes

What this synthesis does NOT compose

The right shape, the wrong shape, the over-shape

What this synthesis composes

What this synthesis does NOT compose

The right shape, the wrong shape, the over-shape

Sign up to practice

What this synthesis composes

What this synthesis does NOT compose

The right shape, the wrong shape, the over-shape

Sign up to practice