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.

Final synthesis — Automation Patterns

Day 28 · ~12 min●

Twenty-seven lessons. Today: tie five together across three tools.

Given items = [{"id": "a", "value": 5}, {"id": "b", "value": 15}, {"id": "c", "value": 25}] and CONFIG = {"threshold": 10}:

Pre-flight — every item has id and value. Abort cleanly otherwise.
Helper — add_event(summary) creates a calendar event and returns the id.
Loop — for each item: if value > threshold, add an event with summary f"alert-{id}".
Structured logging — log each item's outcome with event_id for successes.
Summary — log a summary event at the end with processed, skipped, failed counts.

python

import json

CONFIG = {"threshold": 10}
items = [{"id": "a", "value": 5}, {"id": "b", "value": 15}, {"id": "c", "value": 25}]

def log(event, **fields):
    print(json.dumps({"event": event, **fields}))

# 1. Pre-flight
errors = []
for i, it in enumerate(items):
    if "id" not in it: errors.append((i, "missing id"))
    if "value" not in it: errors.append((i, "missing value"))
if errors:
    log("preflight", errors=errors)
    raise ValueError(f"pre-flight failed: {len(errors)} errors")

# 2. Helper
def add_event(summary):
    result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "calendar_id": "primary",
        "summary": summary,
        "start_datetime": "2026-12-31T10:00:00+00:00",
        "event_duration_minutes": 15,
    })
    return result.get("response_data", {}).get("id") or result.get("id")

# 3-5. Loop with logging and summary
results = {"processed": 0, "skipped": 0, "failed": 0}
for it in items:
    if it["value"] <= CONFIG["threshold"]:
        results["skipped"] += 1
        log("item", id=it["id"], status="skipped")
        continue
    try:
        evt_id = add_event(f"alert-{it['id']}")
        results["processed"] += 1
        log("item", id=it["id"], status="ok", event_id=evt_id)
    except Exception as e:
        results["failed"] += 1
        log("item", id=it["id"], status="failed", error=type(e).__name__)

log("summary", **results)

Five primitives, three tools-worth of pattern, no new concepts.

Same shape every reliable automation has. Pre-flight before side effects. Helpers per tool. Per-item try/except. Structured logs. End-of-run summary. Once you can write this in one sitting on a 3-item input, you can write it on a 3000-item input — same skeleton, more entries in CONFIG, persistent dedup added on top.

What this synthesis composes

Primitive	Lesson	Used for
Pre-flight validation	Day 20	abort if `id` or `value` missing on any item
Configuration	Day 19	`CONFIG["threshold"]` instead of hardcoded `10`
Helper function	Day 27	`add_event(summary)` hides Calendar plumbing
Conditional routing	Day 4	`if value > threshold` decides path
Per-item try/except	Day 13	partial failure handling
Structured logging	Day 14	`log("item", id=..., status=...)` per outcome

Six primitives in one ~30-line script.

Tools touched

Calendar — the side effect (event create)
(Implicit) CONFIG dict — the configuration tool
(Implicit) JSON stdout — the logging "tool"

What this is NOT

Not in scope today (orthogonal, covered earlier or in Advanced):

Persistent state — uses in-memory results, not a Sheet
Retry — every Calendar call assumed to succeed (real production: wrap add_event in retry)
Incremental processing — input is the full 3-item list, no checkpoint
Dedup — items are unique by construction

A real production script would add all four. The skeleton stays the same; you'd insert each primitive at its natural seam:

Retry: inside add_event
Persistent dedup: at top of script (seen = read_state(SHEET)) and before side effect
Incremental: items = filter_since(items, last_run_ts)

Why this lesson exists

Foundations' synthesis (week 3 day 21) covered 4 primitives on 3 items with one tool. Patterns synthesizes 6 primitives on 3 items with the shape of multi-tool — even though the script touches one tool, the helper-per-tool shape and structured logging would scale identically to 3 or 5 tools.

The skill of week 4: write the skeleton automatically. Every primitive has a place; every place has a known idiom.

Day 28 · ~12 min●

Twenty-seven lessons. Today: tie five together across three tools.

Given items = [{"id": "a", "value": 5}, {"id": "b", "value": 15}, {"id": "c", "value": 25}] and CONFIG = {"threshold": 10}:

Pre-flight — every item has id and value. Abort cleanly otherwise.
Helper — add_event(summary) creates a calendar event and returns the id.
Loop — for each item: if value > threshold, add an event with summary f"alert-{id}".
Structured logging — log each item's outcome with event_id for successes.
Summary — log a summary event at the end with processed, skipped, failed counts.

python

import json

CONFIG = {"threshold": 10}
items = [{"id": "a", "value": 5}, {"id": "b", "value": 15}, {"id": "c", "value": 25}]

def log(event, **fields):
    print(json.dumps({"event": event, **fields}))

# 1. Pre-flight
errors = []
for i, it in enumerate(items):
    if "id" not in it: errors.append((i, "missing id"))
    if "value" not in it: errors.append((i, "missing value"))
if errors:
    log("preflight", errors=errors)
    raise ValueError(f"pre-flight failed: {len(errors)} errors")

# 2. Helper
def add_event(summary):
    result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "calendar_id": "primary",
        "summary": summary,
        "start_datetime": "2026-12-31T10:00:00+00:00",
        "event_duration_minutes": 15,
    })
    return result.get("response_data", {}).get("id") or result.get("id")

# 3-5. Loop with logging and summary
results = {"processed": 0, "skipped": 0, "failed": 0}
for it in items:
    if it["value"] <= CONFIG["threshold"]:
        results["skipped"] += 1
        log("item", id=it["id"], status="skipped")
        continue
    try:
        evt_id = add_event(f"alert-{it['id']}")
        results["processed"] += 1
        log("item", id=it["id"], status="ok", event_id=evt_id)
    except Exception as e:
        results["failed"] += 1
        log("item", id=it["id"], status="failed", error=type(e).__name__)

log("summary", **results)

Five primitives, three tools-worth of pattern, no new concepts.

What this synthesis composes

Primitive	Lesson	Used for
Pre-flight validation	Day 20	abort if `id` or `value` missing on any item
Configuration	Day 19	`CONFIG["threshold"]` instead of hardcoded `10`
Helper function	Day 27	`add_event(summary)` hides Calendar plumbing
Conditional routing	Day 4	`if value > threshold` decides path
Per-item try/except	Day 13	partial failure handling
Structured logging	Day 14	`log("item", id=..., status=...)` per outcome

Six primitives in one ~30-line script.

Tools touched

Calendar — the side effect (event create)
(Implicit) CONFIG dict — the configuration tool
(Implicit) JSON stdout — the logging "tool"

What this is NOT

Not in scope today (orthogonal, covered earlier or in Advanced):

Persistent state — uses in-memory results, not a Sheet
Retry — every Calendar call assumed to succeed (real production: wrap add_event in retry)
Incremental processing — input is the full 3-item list, no checkpoint
Dedup — items are unique by construction

A real production script would add all four. The skeleton stays the same; you'd insert each primitive at its natural seam:

Retry: inside add_event
Persistent dedup: at top of script (seen = read_state(SHEET)) and before side effect
Incremental: items = filter_since(items, last_run_ts)

Why this lesson exists

The skill of week 4: write the skeleton automatically. Every primitive has a place; every place has a known idiom.

What this synthesis composes

Tools touched

What this is NOT

Why this lesson exists

What this synthesis composes

Tools touched

What this is NOT

Why this lesson exists

What this synthesis composes

Tools touched

What this is NOT

Why this lesson exists

Sign up to practice

What this synthesis composes

Tools touched

What this is NOT

Why this lesson exists

Sign up to practice