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.

Two Personas: Formal and Casual Rewrites — Ai For Entrepreneurs

Day 17 · ~12 min●

You need to send the same investor update two ways — formal for the board deck, casual for the team Slack. Two windows, two copy-pastes, two prompts. What if you ran both in one function call?

Two agents with different system prompts? One formal rewrite, one casual. Run both on the same text, return both.

Exactly. Two agent instances, two independent calls, one dict back:

python

formal_agent = Agent(model, system_prompt="Rewrite formally.")
casual_agent = Agent(model, system_prompt="Rewrite casually.")
formal = formal_agent.run_sync(text).output
casual = casual_agent.run_sync(text).output
return {"formal": formal, "casual": casual}

Are these two separate model calls? Does that mean twice the cost?

Two calls, yes. Each agent call is independent. The cost is low because the text is short — you're not doubling a large document, you're doubling a short update. Here's the full function:

python

def compare_tones(text: str) -> dict:
    formal_agent = Agent(model, system_prompt="Rewrite formally.")
    casual_agent = Agent(model, system_prompt="Rewrite casually.")
    formal = formal_agent.run_sync(text).output
    casual = casual_agent.run_sync(text).output
    print(f"Formal: {formal[:40]}...")
    return {"formal": formal, "casual": casual}

I'm managing two AI employees with different writing styles. One in a suit, one in a hoodie.

Two personas, one function, one dict. You can extend this to three or four tones — add a technical agent for your engineering blog, a sales agent for the pitch deck version.

I write one update, run this function, and have both the board version and the team version ready. That's an hour back every week.

The dict is a natural unit for multi-output results — {"formal": ..., "casual": ...}. In Week 4 the capstone returns a sorted list of dicts. The pattern of 'multiple results in a structured container' is consistent throughout.

Two Agents, One Function

python

formal_agent = Agent(model, system_prompt="Rewrite formally.")
casual_agent = Agent(model, system_prompt="Rewrite casually.")
return {
    "formal": formal_agent.run_sync(text).output,
    "casual": casual_agent.run_sync(text).output,
}

Pattern

Multiple agents, same input, different system prompts. Results collected into a dict with descriptive keys.

Extension

Add more tones by creating more agents and adding them to the return dict:

"technical" agent for engineering blogs
"sales" agent for pitch deck copy
"brief" agent for push notification text

The calling code stays the same — one dict with more keys.

Day 17 · ~12 min●

You need to send the same investor update two ways — formal for the board deck, casual for the team Slack. Two windows, two copy-pastes, two prompts. What if you ran both in one function call?

Two agents with different system prompts? One formal rewrite, one casual. Run both on the same text, return both.

Exactly. Two agent instances, two independent calls, one dict back:

python

formal_agent = Agent(model, system_prompt="Rewrite formally.")
casual_agent = Agent(model, system_prompt="Rewrite casually.")
formal = formal_agent.run_sync(text).output
casual = casual_agent.run_sync(text).output
return {"formal": formal, "casual": casual}

Are these two separate model calls? Does that mean twice the cost?

Two calls, yes. Each agent call is independent. The cost is low because the text is short — you're not doubling a large document, you're doubling a short update. Here's the full function:

python

def compare_tones(text: str) -> dict:
    formal_agent = Agent(model, system_prompt="Rewrite formally.")
    casual_agent = Agent(model, system_prompt="Rewrite casually.")
    formal = formal_agent.run_sync(text).output
    casual = casual_agent.run_sync(text).output
    print(f"Formal: {formal[:40]}...")
    return {"formal": formal, "casual": casual}

I'm managing two AI employees with different writing styles. One in a suit, one in a hoodie.

Two personas, one function, one dict. You can extend this to three or four tones — add a technical agent for your engineering blog, a sales agent for the pitch deck version.

I write one update, run this function, and have both the board version and the team version ready. That's an hour back every week.

Two Agents, One Function

python

formal_agent = Agent(model, system_prompt="Rewrite formally.")
casual_agent = Agent(model, system_prompt="Rewrite casually.")
return {
    "formal": formal_agent.run_sync(text).output,
    "casual": casual_agent.run_sync(text).output,
}

Pattern

Multiple agents, same input, different system prompts. Results collected into a dict with descriptive keys.

Extension

Add more tones by creating more agents and adding them to the return dict:

"technical" agent for engineering blogs
"sales" agent for pitch deck copy
"brief" agent for push notification text

The calling code stays the same — one dict with more keys.

Two Agents, One Function

Pattern

Extension

Two Agents, One Function

Pattern

Extension

Two Agents, One Function

Pattern

Extension

Sign up to practice

Two Agents, One Function

Pattern

Extension

Sign up to practice