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.

Python for Makers — How Far Did You Come? — Python For Makers

Day 30 · ~11 min●

Thirty days. Twenty-eight functions. A complete log-analysis CLI. Before you close the track — how do you actually feel about these patterns now?

Different. The shapes feel natural. When I see a new problem I can map it to something I've already built — "that's a frequency map," "that's a sliding window," "that's a filter-then-limit."

That's the vocabulary shift. You didn't just absorb syntax — you learned the shapes. Regex, sets, generators, windowed analytics, argparse, pipelines. Rate yourself on the same dimensions as day one and see what moved.

What would a natural next step look like?

Automation for makers — taking these patterns and connecting them to real APIs, event-driven triggers, and scheduled workflows. Every function you built here becomes a call inside a larger, production-grade system.

How Far Did You Come?

Thirty days ago you had Python fundamentals. Now you have a composable toolkit of production patterns you can point at any text or log problem:

Week 1 — str.split with maxsplit, re.search/findall/sub
Week 2 — dict.setdefault grouping, set comprehensions, set intersection, generator windows
Week 3 — streaming yield, merge + sort, chunked batches, retry sentinels, windowed analytics
Week 4 — argparse, filter-then-limit composition, re.compile validation, ASCII tables, capstone pipeline

Every pattern you practiced generalises beyond log analysis — the theme was just the carrier. You now understand exactly how each piece works and how to compose them into real tools.

Self-Assessment

0/6

Not at allSlightlyModeratelyVeryExtremely

1.I can use re.findall() and re.sub() confidently to extract and replace patterns in text.

2.I can split structured text into dicts and build parsers that handle edge cases.

3.I can sort lists of dicts by any key and return the top N results using sorted() and lambda.

4.I can write validation functions that return structured results instead of just crashing.

5.I can process large lists in fixed-size chunks and collect results with extend().

6.I can compose multiple functions into a multi-step data pipeline that handles real-world input.

Day 30 · ~11 min●

Thirty days. Twenty-eight functions. A complete log-analysis CLI. Before you close the track — how do you actually feel about these patterns now?

Different. The shapes feel natural. When I see a new problem I can map it to something I've already built — "that's a frequency map," "that's a sliding window," "that's a filter-then-limit."

What would a natural next step look like?

How Far Did You Come?

Thirty days ago you had Python fundamentals. Now you have a composable toolkit of production patterns you can point at any text or log problem:

Week 1 — str.split with maxsplit, re.search/findall/sub
Week 2 — dict.setdefault grouping, set comprehensions, set intersection, generator windows
Week 3 — streaming yield, merge + sort, chunked batches, retry sentinels, windowed analytics
Week 4 — argparse, filter-then-limit composition, re.compile validation, ASCII tables, capstone pipeline

Every pattern you practiced generalises beyond log analysis — the theme was just the carrier. You now understand exactly how each piece works and how to compose them into real tools.

How Far Did You Come?

Thirty days ago you had Python fundamentals. Now you have a composable toolkit of production patterns you can point at any text or log problem:

Week 1 — str.split with maxsplit, re.search/findall/sub

Week 2 — dict.setdefault grouping, set comprehensions, set intersection, generator windows

Week 3 — streaming yield, merge + sort, chunked batches, retry sentinels, windowed analytics

Week 4 — argparse, filter-then-limit composition, re.compile validation, ASCII tables, capstone pipeline

Every pattern you practiced generalises beyond log analysis — the theme was just the carrier. You now understand exactly how each piece works and how to compose them into real tools.

How Far Did You Come?

Thirty days ago you had Python fundamentals. Now you have a composable toolkit of production patterns you can point at any text or log problem:

Week 1 — str.split with maxsplit, re.search/findall/sub

Week 2 — dict.setdefault grouping, set comprehensions, set intersection, generator windows

Week 3 — streaming yield, merge + sort, chunked batches, retry sentinels, windowed analytics

Week 4 — argparse, filter-then-limit composition, re.compile validation, ASCII tables, capstone pipeline

Every pattern you practiced generalises beyond log analysis — the theme was just the carrier. You now understand exactly how each piece works and how to compose them into real tools.