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.

Categorise Project Status with If/Elif/Else Branching — Python For Freelancers

Day 7 · ~12 min●

is_over_hours from yesterday tells you whether a project is over. But clients need more than a yes or no — they need to know how far over. Three tiers: on track, over by 10%, critical. How do you classify that right now?

I look at the number and make a judgment call. I don't have a consistent threshold. Two clients get different treatment for the same overage.

if/elif/else is that consistent threshold, written once, applied identically to every project. The logic is the same structure as a nested IF in your spreadsheet — but without the formula wrapping:

python

if actual < budgeted * 1.1:
    return "on track"
elif actual < budgeted * 1.25:
    return "over by 10%"
else:
    return "critical"

Why does the order matter? Could I put the else first and check from the top?

Python tests conditions top to bottom and stops at the first True. If you put the broadest condition first, everything falls into it and the elif/else branches never run. Start with the tightest test, widen with each branch:

python

def categorize_project_status(actual: float, budgeted: float) -> str:
    result = "on track" if actual < budgeted * 1.1 else ("over by 10%" if actual < budgeted * 1.25 else "critical")
    print(f"Status: {result}")
    return result

So this replaces the mental gymnastics I do every time I review a project list. One function call and every project gets a consistent label.

Every project. Same thresholds. No judgment call variation. That label feeds directly into Week 2 grouping.

My clients have been getting different risk conversations based on my mood. This makes it consistent.

Consistent thresholds are a deliverable, not just a technical detail. What would you change the 1.25 multiplier to for a client with zero revision tolerance?

If/Elif/Else Branching

Python tests conditions sequentially and short-circuits on the first True:

python

if condition_1:
    # runs if condition_1 is True
elif condition_2:
    # runs if condition_1 is False AND condition_2 is True
else:
    # catch-all — runs when no condition above matched

Order discipline

Put the tightest test first. actual < budgeted * 1.1 is tighter than actual < budgeted * 1.25. If you reverse them, the 10% branch catches everything that is below 25%, and the critical branch never fires.

Multiplier maths

budgeted * 1.1 = 10% over budget. budgeted * 1.25 = 25% over budget.

Day 7 · ~12 min●

I look at the number and make a judgment call. I don't have a consistent threshold. Two clients get different treatment for the same overage.

python

if actual < budgeted * 1.1:
    return "on track"
elif actual < budgeted * 1.25:
    return "over by 10%"
else:
    return "critical"

Why does the order matter? Could I put the else first and check from the top?

python

def categorize_project_status(actual: float, budgeted: float) -> str:
    result = "on track" if actual < budgeted * 1.1 else ("over by 10%" if actual < budgeted * 1.25 else "critical")
    print(f"Status: {result}")
    return result

So this replaces the mental gymnastics I do every time I review a project list. One function call and every project gets a consistent label.

Every project. Same thresholds. No judgment call variation. That label feeds directly into Week 2 grouping.

My clients have been getting different risk conversations based on my mood. This makes it consistent.

Consistent thresholds are a deliverable, not just a technical detail. What would you change the 1.25 multiplier to for a client with zero revision tolerance?

If/Elif/Else Branching

Python tests conditions sequentially and short-circuits on the first True:

python

if condition_1:
    # runs if condition_1 is True
elif condition_2:
    # runs if condition_1 is False AND condition_2 is True
else:
    # catch-all — runs when no condition above matched

Order discipline

Multiplier maths

budgeted * 1.1 = 10% over budget. budgeted * 1.25 = 25% over budget.

def categorize_project_status(actual: float, budgeted: float) -> str: result = "on track" if actual < budgeted * 1.1 else ("over by 10%" if actual < budgeted * 1.25 else "critical") print(f"Status: {result}") return result

If/Elif/Else Branching

Python tests conditions sequentially and short-circuits on the first True:

python

if condition_1:
    # runs if condition_1 is True
elif condition_2:
    # runs if condition_1 is False AND condition_2 is True
else:
    # catch-all — runs when no condition above matched

Order discipline

Multiplier maths

budgeted * 1.1 = 10% over budget. budgeted * 1.25 = 25% over budget.

If/Elif/Else Branching

Python tests conditions sequentially and short-circuits on the first True:

python

if condition_1:
    # runs if condition_1 is True
elif condition_2:
    # runs if condition_1 is False AND condition_2 is True
else:
    # catch-all — runs when no condition above matched

Order discipline

Multiplier maths

budgeted * 1.1 = 10% over budget. budgeted * 1.25 = 25% over budget.