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

Six lessons on observability and long-running: structured JSON logs, counts and timings, threshold alerts, item-level checkpointing, queue-style processing, and the 5-step synthesis.

Week 4 = patterns at scale — dead letters, replay safety, dashboards-as-Sheet, cross-tool consistency, rollback, final synthesis. Ten questions, 80% to pass.

What week 3 covered

Lesson	Concept	Key shape
15	Structured logging	`print(json.dumps({"level": ..., "event": ..., **fields}))`
16	Metrics: counts and timings	`time.monotonic()` + `latency_ms`
17	Threshold alerts	`if metric > threshold: send_alert()`
18	Long-running with status	per-item Sheet checkpoint
19	Queue-style processing	`deque.popleft` + status transitions
20	Synthesis	verify → parse → dedupe → dispatch → log

Week 4 = patterns at scale.

Sign up to practice

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

Day 22 · ~11 min●

Six lessons on observability and long-running: structured JSON logs, counts and timings, threshold alerts, item-level checkpointing, queue-style processing, and the 5-step synthesis.

Week 4 = patterns at scale — dead letters, replay safety, dashboards-as-Sheet, cross-tool consistency, rollback, final synthesis. Ten questions, 80% to pass.

What week 3 covered

Lesson	Concept	Key shape
15	Structured logging	`print(json.dumps({"level": ..., "event": ..., **fields}))`
16	Metrics: counts and timings	`time.monotonic()` + `latency_ms`
17	Threshold alerts	`if metric > threshold: send_alert()`
18	Long-running with status	per-item Sheet checkpoint
19	Queue-style processing	`deque.popleft` + status transitions
20	Synthesis	verify → parse → dedupe → dispatch → log

Week 4 = patterns at scale.

What week 3 covered

Lesson	Concept	Key shape
15	Structured logging	`print(json.dumps({"level": ..., "event": ..., **fields}))`
16	Metrics: counts and timings	`time.monotonic()` + `latency_ms`
17	Threshold alerts	`if metric > threshold: send_alert()`
18	Long-running with status	per-item Sheet checkpoint
19	Queue-style processing	`deque.popleft` + status transitions
20	Synthesis	verify → parse → dedupe → dispatch → log

Week 4 = patterns at scale.

What week 3 covered

Lesson	Concept	Key shape
15	Structured logging	`print(json.dumps({"level": ..., "event": ..., **fields}))`
16	Metrics: counts and timings	`time.monotonic()` + `latency_ms`
17	Threshold alerts	`if metric > threshold: send_alert()`
18	Long-running with status	per-item Sheet checkpoint
19	Queue-style processing	`deque.popleft` + status transitions
20	Synthesis	verify → parse → dedupe → dispatch → log

Week 4 = patterns at scale.