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

You can filter respondents, group by treatment, and serialise to JSON. Every workflow you own still runs inside apps: Gmail for co-author coordination, Sheets for citation logs, Calendar for submission deadlines. This week you bridge Python to those apps. One function call returns your actual inbox.

I understand the Python side. But connecting to Gmail sounds like it needs OAuth tokens, API keys, a lot of setup I haven't configured before.

The plumbing is already handled. Composio takes care of the OAuth handshake. On your side it's one call: toolset.execute_action(Action.GMAIL_FETCH_EMAILS, {"max_results": 20}). The dict that comes back contains your real subjects, real senders, real timestamps.

Wait — that response is my actual inbox? Not a sandbox or fixture file?

Your inbox. Right now. Every run. That's why Gmail is first — there's no better way to make automation feel real than watching your own co-author emails come back in a Python console. This week: count, fetch, search, draft, send. Five verbs, five days.

This Week

Day 3 — count emails in your inbox
Day 4 — fetch a message's subject and sender by ID
Day 5 — search with a Gmail query string (from:, is:unread)
Day 6 — create a draft in your Drafts folder
Day 7 — send an email to yourself

Goal: By Friday you can name every Gmail action you'll need for the literature-search pipeline capstone.

Sign up to practice

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

Day 2 · ~11 min●

I understand the Python side. But connecting to Gmail sounds like it needs OAuth tokens, API keys, a lot of setup I haven't configured before.

Wait — that response is my actual inbox? Not a sandbox or fixture file?

This Week

Day 3 — count emails in your inbox
Day 4 — fetch a message's subject and sender by ID
Day 5 — search with a Gmail query string (from:, is:unread)
Day 6 — create a draft in your Drafts folder
Day 7 — send an email to yourself

Goal: By Friday you can name every Gmail action you'll need for the literature-search pipeline capstone.

This Week

Day 3 — count emails in your inbox

Day 4 — fetch a message's subject and sender by ID

Day 5 — search with a Gmail query string (from:, is:unread)

Day 6 — create a draft in your Drafts folder

Day 7 — send an email to yourself

Goal: By Friday you can name every Gmail action you'll need for the literature-search pipeline capstone.

This Week

Day 3 — count emails in your inbox

Day 4 — fetch a message's subject and sender by ID

Day 5 — search with a Gmail query string (from:, is:unread)

Day 6 — create a draft in your Drafts folder

Day 7 — send an email to yourself

Goal: By Friday you can name every Gmail action you'll need for the literature-search pipeline capstone.

This Week

Week 1

Sign up to practice

This Week

This Week

Week 1

Sign up to practice

This Week