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

Six lessons on the class layer. Eight questions, 80% to pass. The questions test design tradeoffs as much as syntax — when a class earns its place, when @dataclass saves you, when type hints actually run.

Let's go.

What week 1 covered

Lesson	Concept	Key syntax
1	When a dict isn't enough	dicts-of-dicts hurt at scale
2	`class` and `__init__`	`class Item: def __init__(self, name, value): ...`
3	Methods	`def is_high(self): return self.value > 10`
4	`@dataclass`	`@dataclass class Item: name: str; value: int`
5	Type hints	`def add(a: int, b: int) -> int:`
6	When NOT to use a class	functional alternatives — three signals

Three signals a class earns its place

Repeated shape — list of similar items
Behaviour bundled with data — methods on the same shape
Identity matters — two instances with the same data are still distinct

If none apply, prefer functions and tuples/dicts.

Sign up to practice

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

Day 8 · ~11 min●

Let's go.

What week 1 covered

Lesson	Concept	Key syntax
1	When a dict isn't enough	dicts-of-dicts hurt at scale
2	`class` and `__init__`	`class Item: def __init__(self, name, value): ...`
3	Methods	`def is_high(self): return self.value > 10`
4	`@dataclass`	`@dataclass class Item: name: str; value: int`
5	Type hints	`def add(a: int, b: int) -> int:`
6	When NOT to use a class	functional alternatives — three signals

Three signals a class earns its place

Repeated shape — list of similar items
Behaviour bundled with data — methods on the same shape
Identity matters — two instances with the same data are still distinct

If none apply, prefer functions and tuples/dicts.

What week 1 covered

Lesson	Concept	Key syntax
1	When a dict isn't enough	dicts-of-dicts hurt at scale
2	`class` and `__init__`	`class Item: def __init__(self, name, value): ...`
3	Methods	`def is_high(self): return self.value > 10`
4	`@dataclass`	`@dataclass class Item: name: str; value: int`
5	Type hints	`def add(a: int, b: int) -> int:`
6	When NOT to use a class	functional alternatives — three signals

What week 1 covered

Lesson	Concept	Key syntax
1	When a dict isn't enough	dicts-of-dicts hurt at scale
2	`class` and `__init__`	`class Item: def __init__(self, name, value): ...`
3	Methods	`def is_high(self): return self.value > 10`
4	`@dataclass`	`@dataclass class Item: name: str; value: int`
5	Type hints	`def add(a: int, b: int) -> int:`
6	When NOT to use a class	functional alternatives — three signals