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.

Side effect: update — Automation Foundations

Day 12 · ~11 min●

Day 10 created an event and got its ID. Day 12 uses that ID to update the event — change its summary, time, or description. Two-call shape: create-then-update.

python

# Step 1: create (we did this on day 10 — same shape, fresh event)
created = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "calendar_id": "primary",
    "summary": "zuzu-day-12 (will be updated)",
    "start_datetime": "2026-12-31T11:00:00+00:00",
    "event_duration_minutes": 30,
})
event_id = created.get("response_data", {}).get("id") or created.get("id")

# Step 2: update — modify the summary
result = toolset.execute_action(Action.GOOGLECALENDAR_UPDATE_EVENT, {
    "calendar_id": "primary",
    "event_id": event_id,
    "summary": "zuzu-day-12 (updated)",
    "start_datetime": "2026-12-31T11:00:00+00:00",
    "event_duration_minutes": 30,
})
print(result.get("summary"))

The update API takes the same parameters as create, plus event_id?

Roughly. Some APIs allow partial updates (only changed fields); others want the full record. Calendar's update wants the full event record — fields not included get overwritten with their defaults. Always pass at least the same fields you set on create, or you risk wiping them.

And the verification?

Asserts result.get("summary") == "zuzu-day-12 (updated)" — confirms the update landed and we got the new value back. The API only returns the new summary if the update actually wrote it.

Side effect: update

Updates take an existing resource and change one or more of its fields. They almost always need:

The resource's ID (from a prior create or list call)
The fields you want to change (and often the fields you want to keep — see partial vs full update below)

Partial vs full update

Different APIs treat the request body differently:

Full update: send the entire resource. Anything you omit gets reset. (Calendar UPDATE_EVENT works this way.)
Partial update / patch: send only what's changing. Omitted fields keep their existing values. (Some APIs.)

When in doubt, send the full record — safer.

Preserving the create→update flow in one script

In one script, just save the ID from create into a variable:

python

created = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, { ... })
event_id = created.get("response_data", {}).get("id") or created.get("id")

toolset.execute_action(Action.GOOGLECALENDAR_UPDATE_EVENT, {
    "calendar_id": "primary",
    "event_id": event_id,
    ...
})

In a multi-run script, you'd persist event_id somewhere (Sheet, Notion page, file) so the update step on a later run knows which event to touch. That's Auto Intermediate territory.

Verification

python

assert result.get("summary") == "zuzu-day-12 (updated)"

The response from UPDATE_EVENT echoes the updated record. If our new summary is in the response, the write committed.

Don't update without confirming the create

If event_id is None (because create silently failed or returned an unexpected shape), the update call will fail with a confusing error. Defensive:

python

if not event_id:
    raise RuntimeError(f"create returned no id: {created!r}")

A two-line guard saves a 20-minute debug session.

Day 12 · ~11 min●

Day 10 created an event and got its ID. Day 12 uses that ID to update the event — change its summary, time, or description. Two-call shape: create-then-update.

python

# Step 1: create (we did this on day 10 — same shape, fresh event)
created = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, {
    "calendar_id": "primary",
    "summary": "zuzu-day-12 (will be updated)",
    "start_datetime": "2026-12-31T11:00:00+00:00",
    "event_duration_minutes": 30,
})
event_id = created.get("response_data", {}).get("id") or created.get("id")

# Step 2: update — modify the summary
result = toolset.execute_action(Action.GOOGLECALENDAR_UPDATE_EVENT, {
    "calendar_id": "primary",
    "event_id": event_id,
    "summary": "zuzu-day-12 (updated)",
    "start_datetime": "2026-12-31T11:00:00+00:00",
    "event_duration_minutes": 30,
})
print(result.get("summary"))

The update API takes the same parameters as create, plus event_id?

And the verification?

Asserts result.get("summary") == "zuzu-day-12 (updated)" — confirms the update landed and we got the new value back. The API only returns the new summary if the update actually wrote it.

Side effect: update

Updates take an existing resource and change one or more of its fields. They almost always need:

The resource's ID (from a prior create or list call)
The fields you want to change (and often the fields you want to keep — see partial vs full update below)

Partial vs full update

Different APIs treat the request body differently:

Full update: send the entire resource. Anything you omit gets reset. (Calendar UPDATE_EVENT works this way.)
Partial update / patch: send only what's changing. Omitted fields keep their existing values. (Some APIs.)

When in doubt, send the full record — safer.

Preserving the create→update flow in one script

In one script, just save the ID from create into a variable:

python

created = toolset.execute_action(Action.GOOGLECALENDAR_CREATE_EVENT, { ... })
event_id = created.get("response_data", {}).get("id") or created.get("id")

toolset.execute_action(Action.GOOGLECALENDAR_UPDATE_EVENT, {
    "calendar_id": "primary",
    "event_id": event_id,
    ...
})

In a multi-run script, you'd persist event_id somewhere (Sheet, Notion page, file) so the update step on a later run knows which event to touch. That's Auto Intermediate territory.

Verification

python

assert result.get("summary") == "zuzu-day-12 (updated)"

The response from UPDATE_EVENT echoes the updated record. If our new summary is in the response, the write committed.

Don't update without confirming the create

If event_id is None (because create silently failed or returned an unexpected shape), the update call will fail with a confusing error. Defensive:

python

if not event_id:
    raise RuntimeError(f"create returned no id: {created!r}")

A two-line guard saves a 20-minute debug session.

Side effect: update

Partial vs full update

Preserving the create→update flow in one script

Verification

Don't update without confirming the create

Side effect: update

Partial vs full update

Preserving the create→update flow in one script

Verification

Don't update without confirming the create

Side effect: update

Partial vs full update

Preserving the create→update flow in one script

Verification

Don't update without confirming the create

Sign up to practice

Side effect: update

Partial vs full update

Preserving the create→update flow in one script

Verification

Don't update without confirming the create

Sign up to practice