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.

Bulk Create With Retry AND Checkpoint Logging — Automation For Makers

Day 27 · ~12 min●

You have bulk create from Day 20, retry from Day 19, checkpointing from Day 25. Today you combine all three. Each title gets retried; each outcome gets recorded in a checkpoint list the caller can use to resume. What's the return shape?

The checkpoint shape from Day 25 — a list of [title, True/False] pairs?

Exactly. The title is the step name, the boolean flags success. The caller reads the checkpoint back and uses resume_from_checkpoint on the next run to skip what already worked:

python

for title in titles:
    ok = False
    for attempt in range(1, max_attempts + 1):
        try:
            toolset.execute_action(Action.GOOGLETASKS_CREATE_TASK, {"title": title})
            ok = True
            break
        except Exception:
            pass
    checkpoint.append([title, ok])

So the retry inner loop sets ok to True on success — if every attempt fails, ok stays False and that title's checkpoint entry reflects the failure.

Right. Every title ends up in the checkpoint list with its final state. Here's the full function:

python

def safe_bulk_create_with_checkpoint(titles: list, max_attempts: int) -> list:
    checkpoint = []
    for title in titles:
        ok = False
        for attempt in range(1, max_attempts + 1):
            try:
                toolset.execute_action(Action.GOOGLETASKS_CREATE_TASK, {"title": title})
                ok = True
                break
            except Exception as exc:
                if attempt == max_attempts:
                    print(f"Title '{title}' failed after {max_attempts} attempts: {exc}")
        checkpoint.append([title, ok])
    succeeded = sum(1 for _, ok in checkpoint if ok)
    print(f"Bulk create: {succeeded}/{len(titles)} succeeded, checkpoint has {len(checkpoint)} entries")
    return checkpoint

If I run this again tomorrow with the same titles plus one new one, how does the caller handle it?

The caller loads yesterday's checkpoint, runs resume_from_checkpoint(titles, yesterday_checkpoint) to find the ones still needing work, and passes that reduced list to this function. Combined with idempotent create, every rerun is safe and fast.

So three patterns from three days — retry, bulk, checkpoint — now compose into one function that can pause and resume?

That is the pipeline primitive Day 28's capstone uses. Retry plus checkpoints is the shape every resumable automation needs.

Three Patterns, One Function

TL;DR: Bulk + retry + checkpoint = resumable writes. Each title has up to N attempts, the outcome is recorded as [title, bool].

Outer loop — iterates titles
Inner retry loop — up to max_attempts per title
Checkpoint append — records every outcome, good or bad

Caller workflow

Step	Call
first run	pass full title list
resume	`resume_from_checkpoint` → reduced list → same function

Day 27 · ~12 min●

The checkpoint shape from Day 25 — a list of [title, True/False] pairs?

Exactly. The title is the step name, the boolean flags success. The caller reads the checkpoint back and uses resume_from_checkpoint on the next run to skip what already worked:

python

for title in titles:
    ok = False
    for attempt in range(1, max_attempts + 1):
        try:
            toolset.execute_action(Action.GOOGLETASKS_CREATE_TASK, {"title": title})
            ok = True
            break
        except Exception:
            pass
    checkpoint.append([title, ok])

So the retry inner loop sets ok to True on success — if every attempt fails, ok stays False and that title's checkpoint entry reflects the failure.

Right. Every title ends up in the checkpoint list with its final state. Here's the full function:

python

def safe_bulk_create_with_checkpoint(titles: list, max_attempts: int) -> list:
    checkpoint = []
    for title in titles:
        ok = False
        for attempt in range(1, max_attempts + 1):
            try:
                toolset.execute_action(Action.GOOGLETASKS_CREATE_TASK, {"title": title})
                ok = True
                break
            except Exception as exc:
                if attempt == max_attempts:
                    print(f"Title '{title}' failed after {max_attempts} attempts: {exc}")
        checkpoint.append([title, ok])
    succeeded = sum(1 for _, ok in checkpoint if ok)
    print(f"Bulk create: {succeeded}/{len(titles)} succeeded, checkpoint has {len(checkpoint)} entries")
    return checkpoint

If I run this again tomorrow with the same titles plus one new one, how does the caller handle it?

So three patterns from three days — retry, bulk, checkpoint — now compose into one function that can pause and resume?

That is the pipeline primitive Day 28's capstone uses. Retry plus checkpoints is the shape every resumable automation needs.

Three Patterns, One Function

TL;DR: Bulk + retry + checkpoint = resumable writes. Each title has up to N attempts, the outcome is recorded as [title, bool].

Outer loop — iterates titles
Inner retry loop — up to max_attempts per title
Checkpoint append — records every outcome, good or bad

Caller workflow

Step	Call
first run	pass full title list
resume	`resume_from_checkpoint` → reduced list → same function

for title in titles: ok = False for attempt in range(1, max_attempts + 1): try: toolset.execute_action(Action.GOOGLETASKS_CREATE_TASK, {"title": title}) ok = True break except Exception: pass checkpoint.append([title, ok])

def safe_bulk_create_with_checkpoint(titles: list, max_attempts: int) -> list: checkpoint = [] for title in titles: ok = False for attempt in range(1, max_attempts + 1): try: toolset.execute_action(Action.GOOGLETASKS_CREATE_TASK, {"title": title}) ok = True break except Exception as exc: if attempt == max_attempts: print(f"Title '{title}' failed after {max_attempts} attempts: {exc}") checkpoint.append([title, ok]) succeeded = sum(1 for _, ok in checkpoint if ok) print(f"Bulk create: {succeeded}/{len(titles)} succeeded, checkpoint has {len(checkpoint)} entries") return checkpoint

Three Patterns, One Function

TL;DR: Bulk + retry + checkpoint = resumable writes. Each title has up to N attempts, the outcome is recorded as [title, bool].

Outer loop — iterates titles

Inner retry loop — up to max_attempts per title

Checkpoint append — records every outcome, good or bad

Caller workflow

Step	Call
first run	pass full title list
resume	`resume_from_checkpoint` → reduced list → same function

Three Patterns, One Function

TL;DR: Bulk + retry + checkpoint = resumable writes. Each title has up to N attempts, the outcome is recorded as [title, bool].

Outer loop — iterates titles

Inner retry loop — up to max_attempts per title

Checkpoint append — records every outcome, good or bad

Caller workflow

Step	Call
first run	pass full title list
resume	`resume_from_checkpoint` → reduced list → same function

Three Patterns, One Function

Caller workflow

Three Patterns, One Function

Caller workflow

Three Patterns, One Function

Caller workflow

Sign up to practice

Three Patterns, One Function

Caller workflow

Sign up to practice