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.

Filter → Act — Automation Foundations

Day 17 · ~11 min●

Read 5 messages. Create a Calendar event for any whose subject contains the word urgent. Day 4's filtering pattern + day 9's create + a counter to verify how many fired.

python

result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 5})
messages = result.get("messages", [])

sent_count = 0
for m in messages:
    subject = m.get("subject", "")
    if "urgent" in subject.lower():
        toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
            "calendar_id": "primary",
            "summary": f"Urgent: {subject}",
            "start_datetime": "2026-12-31T09:00:00+00:00",
            "event_duration_minutes": 15,
        })
        sent_count += 1

print(f"sent {sent_count} alerts")

subject.lower() — to make the match case-insensitive?

Right. Real subjects might be URGENT or Urgent or urgent. Lowercasing both sides of the comparison normalizes. Without it you'd miss Urgent: Q4 Report.

And nothing fires if no message matches?

That's the design. No matching subject = no event created. sent_count == 0 means nothing matched — which is correct behaviour, not a bug.

Filter → Act

The shape:

Read a list from API A.
Filter to the items that satisfy a condition.
For each surviving item, fire a side-effect call to API B.
(Often:) count how many fired.

The pattern in code

python

for item in items:
    if matches_condition(item):
        do_side_effect(item)

The filter and the side effect are tied together — neither makes sense without the other in this lesson. (Pure filter without side effect = day 4. Side effect on every item = day 8. Together = day 17.)

Case-insensitive matching

Real-world strings are messy. "URGENT: ...", "Urgent: ...", "urgent: ..." — same intent, different casing. Normalize:

python

if "urgent" in subject.lower():    # always works regardless of how the user typed it

For more sophisticated matching (whole word, regex), reach for the re module. For one-keyword case-insensitive, lowercase + in is enough.

Counter pattern

python

sent_count = 0
for item in items:
    if matches:
        side_effect(item)
        sent_count += 1    # the `+= 1` is shorthand for `sent_count = sent_count + 1`

Reporting how many side effects fired is good practice. If a script is supposed to alert five customers and the count is 0, that's an immediate signal something's off.

Filter zero — graceful silence

When the list is empty (or nothing matches), the loop body never runs. No side effect. No noise. That's correct — "only alert when urgent" means "don't alert when not urgent". Don't add a fallback print("no urgent items") unless you actually want that signal.

Day 17 · ~11 min●

Read 5 messages. Create a Calendar event for any whose subject contains the word urgent. Day 4's filtering pattern + day 9's create + a counter to verify how many fired.

python

result = toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 5})
messages = result.get("messages", [])

sent_count = 0
for m in messages:
    subject = m.get("subject", "")
    if "urgent" in subject.lower():
        toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
            "calendar_id": "primary",
            "summary": f"Urgent: {subject}",
            "start_datetime": "2026-12-31T09:00:00+00:00",
            "event_duration_minutes": 15,
        })
        sent_count += 1

print(f"sent {sent_count} alerts")

subject.lower() — to make the match case-insensitive?

Right. Real subjects might be URGENT or Urgent or urgent. Lowercasing both sides of the comparison normalizes. Without it you'd miss Urgent: Q4 Report.

And nothing fires if no message matches?

That's the design. No matching subject = no event created. sent_count == 0 means nothing matched — which is correct behaviour, not a bug.

Filter → Act

The shape:

Read a list from API A.
Filter to the items that satisfy a condition.
For each surviving item, fire a side-effect call to API B.
(Often:) count how many fired.

The pattern in code

python

for item in items:
    if matches_condition(item):
        do_side_effect(item)

Case-insensitive matching

Real-world strings are messy. "URGENT: ...", "Urgent: ...", "urgent: ..." — same intent, different casing. Normalize:

python

if "urgent" in subject.lower():    # always works regardless of how the user typed it

For more sophisticated matching (whole word, regex), reach for the re module. For one-keyword case-insensitive, lowercase + in is enough.

Counter pattern

python

sent_count = 0
for item in items:
    if matches:
        side_effect(item)
        sent_count += 1    # the `+= 1` is shorthand for `sent_count = sent_count + 1`

Reporting how many side effects fired is good practice. If a script is supposed to alert five customers and the count is 0, that's an immediate signal something's off.

Filter → Act

The pattern in code

Case-insensitive matching

Counter pattern

Filter zero — graceful silence

Filter → Act

The pattern in code

Case-insensitive matching

Counter pattern

Filter zero — graceful silence

Filter → Act

The pattern in code

Case-insensitive matching

Counter pattern

Filter zero — graceful silence

Sign up to practice

Filter → Act

The pattern in code

Case-insensitive matching

Counter pattern

Filter zero — graceful silence

Sign up to practice