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

You can read events off your calendar. Today you add one from code. What's the shape of an event's payload going in?

A title (summary) and a time range — a start and an end? Probably as ISO datetime strings?

Exactly. GOOGLECALENDAR_CREATE_EVENT takes summary plus start and end as nested dicts keyed by dateTime. ISO 8601 is the shared format — "2026-05-01T10:00:00":

python

result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "summary": "Planning block",
    "start": {"dateTime": "2026-05-01T10:00:00"},
    "end": {"dateTime": "2026-05-01T11:00:00"},
})

The caller passes a date string like 2026-05-01. I need to append T10:00:00 to form the full ISO timestamp?

Simplest path — concatenate the time to the date inside the function. You pick a default hour for the block so the caller only has to think about the day:

python

def create_event(title: str, start_date: str) -> dict:
    result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "summary": title,
        "start": {"dateTime": start_date + "T10:00:00"},
        "end": {"dateTime": start_date + "T11:00:00"},
    })
    return result

Why wrap dateTime in a dict at all? Why not just pass the string directly?

Calendar events support time zones, all-day events, and recurring patterns — the nested dict leaves room for those extra fields. {"dateTime": ...} is the shape the API expects; adding "timeZone": "America/Los_Angeles" later is one more key, no restructuring.

So after this function runs, the event actually appears on my calendar — I can open Google Calendar in my browser and see it?

Open your Calendar tab after the test runs. The block you created will be sitting there at 10 AM. Automation stops being theoretical the moment you see your calendar change.

Writing to Calendar

TL;DR: Wrap datetimes in {"dateTime": "..."} dicts so you can add time zones or switch to all-day later.

Action enum — Action.GOOGLECALENDAR_CREATE_EVENT
Summary — the event title that shows in the agenda
Start/end — nested dicts with ISO 8601 strings
Return dict — includes the new event's id, summary, status
Extensible — drop in timeZone or location later as sibling keys

ISO 8601 shape

Field	Example
Date only	`"2026-05-01"`
DateTime	`"2026-05-01T10:00:00"`

Day 12 · ~12 min●

You can read events off your calendar. Today you add one from code. What's the shape of an event's payload going in?

A title (summary) and a time range — a start and an end? Probably as ISO datetime strings?

Exactly. GOOGLECALENDAR_CREATE_EVENT takes summary plus start and end as nested dicts keyed by dateTime. ISO 8601 is the shared format — "2026-05-01T10:00:00":

python

result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "summary": "Planning block",
    "start": {"dateTime": "2026-05-01T10:00:00"},
    "end": {"dateTime": "2026-05-01T11:00:00"},
})

The caller passes a date string like 2026-05-01. I need to append T10:00:00 to form the full ISO timestamp?

Simplest path — concatenate the time to the date inside the function. You pick a default hour for the block so the caller only has to think about the day:

python

def create_event(title: str, start_date: str) -> dict:
    result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "summary": title,
        "start": {"dateTime": start_date + "T10:00:00"},
        "end": {"dateTime": start_date + "T11:00:00"},
    })
    return result

Why wrap dateTime in a dict at all? Why not just pass the string directly?

Calendar events support time zones, all-day events, and recurring patterns — the nested dict leaves room for those extra fields. {"dateTime": ...} is the shape the API expects; adding "timeZone": "America/Los_Angeles" later is one more key, no restructuring.

So after this function runs, the event actually appears on my calendar — I can open Google Calendar in my browser and see it?

Open your Calendar tab after the test runs. The block you created will be sitting there at 10 AM. Automation stops being theoretical the moment you see your calendar change.

Writing to Calendar

TL;DR: Wrap datetimes in {"dateTime": "..."} dicts so you can add time zones or switch to all-day later.

Action enum — Action.GOOGLECALENDAR_CREATE_EVENT
Summary — the event title that shows in the agenda
Start/end — nested dicts with ISO 8601 strings
Return dict — includes the new event's id, summary, status
Extensible — drop in timeZone or location later as sibling keys

ISO 8601 shape

Field	Example
Date only	`"2026-05-01"`
DateTime	`"2026-05-01T10:00:00"`

Day 12 · ~12 min●

You can read events off your calendar. Today you add one from code. What's the shape of an event's payload going in?

A title (summary) and a time range — a start and an end? Probably as ISO datetime strings?

Exactly. GOOGLECALENDAR_CREATE_EVENT takes summary plus start and end as nested dicts keyed by dateTime. ISO 8601 is the shared format — "2026-05-01T10:00:00":

python

result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "summary": "Planning block",
    "start": {"dateTime": "2026-05-01T10:00:00"},
    "end": {"dateTime": "2026-05-01T11:00:00"},
})

The caller passes a date string like 2026-05-01. I need to append T10:00:00 to form the full ISO timestamp?

Simplest path — concatenate the time to the date inside the function. You pick a default hour for the block so the caller only has to think about the day:

python

def create_event(title: str, start_date: str) -> dict:
    result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "summary": title,
        "start": {"dateTime": start_date + "T10:00:00"},
        "end": {"dateTime": start_date + "T11:00:00"},
    })
    return result

Why wrap dateTime in a dict at all? Why not just pass the string directly?

Calendar events support time zones, all-day events, and recurring patterns — the nested dict leaves room for those extra fields. {"dateTime": ...} is the shape the API expects; adding "timeZone": "America/Los_Angeles" later is one more key, no restructuring.

So after this function runs, the event actually appears on my calendar — I can open Google Calendar in my browser and see it?

Open your Calendar tab after the test runs. The block you created will be sitting there at 10 AM. Automation stops being theoretical the moment you see your calendar change.

Writing to Calendar

TL;DR: Wrap datetimes in {"dateTime": "..."} dicts so you can add time zones or switch to all-day later.

Action enum — Action.GOOGLECALENDAR_CREATE_EVENT
Summary — the event title that shows in the agenda
Start/end — nested dicts with ISO 8601 strings
Return dict — includes the new event's id, summary, status
Extensible — drop in timeZone or location later as sibling keys

ISO 8601 shape

Field	Example
Date only	`"2026-05-01"`
DateTime	`"2026-05-01T10:00:00"`

Sign up to practice

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

or

Day 12 · ~12 min●

You can read events off your calendar. Today you add one from code. What's the shape of an event's payload going in?

A title (summary) and a time range — a start and an end? Probably as ISO datetime strings?

Exactly. GOOGLECALENDAR_CREATE_EVENT takes summary plus start and end as nested dicts keyed by dateTime. ISO 8601 is the shared format — "2026-05-01T10:00:00":

python

result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "summary": "Planning block",
    "start": {"dateTime": "2026-05-01T10:00:00"},
    "end": {"dateTime": "2026-05-01T11:00:00"},
})

The caller passes a date string like 2026-05-01. I need to append T10:00:00 to form the full ISO timestamp?

Simplest path — concatenate the time to the date inside the function. You pick a default hour for the block so the caller only has to think about the day:

python

def create_event(title: str, start_date: str) -> dict:
    result = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
        "summary": title,
        "start": {"dateTime": start_date + "T10:00:00"},
        "end": {"dateTime": start_date + "T11:00:00"},
    })
    return result

Why wrap dateTime in a dict at all? Why not just pass the string directly?

Calendar events support time zones, all-day events, and recurring patterns — the nested dict leaves room for those extra fields. {"dateTime": ...} is the shape the API expects; adding "timeZone": "America/Los_Angeles" later is one more key, no restructuring.

So after this function runs, the event actually appears on my calendar — I can open Google Calendar in my browser and see it?

Open your Calendar tab after the test runs. The block you created will be sitting there at 10 AM. Automation stops being theoretical the moment you see your calendar change.

Writing to Calendar

TL;DR: Wrap datetimes in {"dateTime": "..."} dicts so you can add time zones or switch to all-day later.

Action enum — Action.GOOGLECALENDAR_CREATE_EVENT
Summary — the event title that shows in the agenda
Start/end — nested dicts with ISO 8601 strings
Return dict — includes the new event's id, summary, status
Extensible — drop in timeZone or location later as sibling keys

ISO 8601 shape

Field	Example
Date only	`"2026-05-01"`
DateTime	`"2026-05-01T10:00:00"`

Privacy Terms

Sign up to practice

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

or