Question 1

How much does zuzu.codes cost?

Accepted Answer

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.

Question 2

How long does each track take?

Accepted Answer

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.

Question 3

What's the lesson format?

Accepted Answer

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.

Question 4

Do I need prior coding experience?

Accepted Answer

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.

Question 5

How is zuzu.codes different from freeCodeCamp or Codecademy?

Accepted Answer

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.

Lesson	Concept
22	Prompt versioning — registry of `purpose_vN`, every answer tagged with version
23	A/B prompt testing — same eval cases, two versions, compare pass rates
24	Cost dashboards — log per-call metrics, summarise, optionally write to a Sheet
25	Guardrail composition — stack PII / retry / fallback as nested wrappers
26	Agent observability — trace per run, event sequence, audit trail
27	Final integration — versioned prompt + tracked call + trace + side-effect log

Lesson	Concept
22	Prompt versioning — registry of `purpose_vN`, every answer tagged with version
23	A/B prompt testing — same eval cases, two versions, compare pass rates
24	Cost dashboards — log per-call metrics, summarise, optionally write to a Sheet
25	Guardrail composition — stack PII / retry / fallback as nested wrappers
26	Agent observability — trace per run, event sequence, audit trail
27	Final integration — versioned prompt + tracked call + trace + side-effect log

Lesson	Concept
22	Prompt versioning — registry of `purpose_vN`, every answer tagged with version
23	A/B prompt testing — same eval cases, two versions, compare pass rates
24	Cost dashboards — log per-call metrics, summarise, optionally write to a Sheet
25	Guardrail composition — stack PII / retry / fallback as nested wrappers
26	Agent observability — trace per run, event sequence, audit trail
27	Final integration — versioned prompt + tracked call + trace + side-effect log

Lesson	Concept
22	Prompt versioning — registry of `purpose_vN`, every answer tagged with version
23	A/B prompt testing — same eval cases, two versions, compare pass rates
24	Cost dashboards — log per-call metrics, summarise, optionally write to a Sheet
25	Guardrail composition — stack PII / retry / fallback as nested wrappers
26	Agent observability — trace per run, event sequence, audit trail
27	Final integration — versioned prompt + tracked call + trace + side-effect log

What week 4 covered

Sign up to practice

What week 4 covered

What week 4 covered

Sign up to practice

What week 4 covered