Skip to content
Check if a number is evenAnd you need it in 5 different places
Hard to maintainEasy to make mistakesChanges need to be made everywhere
Input → money + selectionProcessing → internal logicOutput → item
A named block of codeThat takes inputDoes some workReturns output
Jumps to function definitionAssigns a = 3, b = 4Runs function bodyReturns valueComes back to where it was called
Parameters → variables in function definitionArguments → actual values passed
Cannot reuse resultCannot test easily
Function to check evenFunction to count
Forgetting returnPrinting inside functionUsing global variablesConfusing parameters and argumentsWriting very large functions
For max: assume first elementFor sum: start with 0Vowels: a, e, i, o, uPrime: check divisibility from 2 to n-1String reverse: build new string or loop backwardsAvoid global variables
Write reusable codeBreak problems into smaller partsUnderstand function flowUse return values properlyCombine functions to solve bigger problems
Why do functions improve code quality?What happens when a function is called?Difference between return and print?Why should functions be small?
DictionariesKey-value thinkingReal-world data modelingFirst step toward databases
Zeni Study
- Pages
Share
Explore
Day 4 — Functions
🟢 Day 4 — Functions (Thinking in Reusable Blocks)
1️⃣ Why Do We Need Functions?
Imagine this situation:
You wrote code to:
Without Functions (Bad)
if n % 2 == 0:
print("Even")
Repeated again and again.
Problems:
💡 If logic is repeated → it deserves a function
2️⃣ Real-World Analogy
Think of a vending machine.
You don’t care how it works inside.
🧠 A function hides complexity and exposes behavior.
3️⃣ What Is a Function?
A function is:
def add(a, b):
return a + b
4️⃣ How Computer Thinks About Functions
When Python sees:
add(3, 4)
It:
🧠 Execution jumps, then returns.
5️⃣ Parameters vs Arguments (Important Clarity)
def multiply(x, y): # parameters
return x * y
multiply(3, 5) # arguments
6️⃣ return vs print (CRITICAL CONCEPT)
❌ Bad Practice
def add(a, b):
print(a + b)
Why bad?
✅ Correct Practice
def add(a, b):
return a + b
🧠 Functions should return values, not print.
7️⃣ Using Functions Inside Functions
def is_even(n):
return n % 2 == 0
def count_even(numbers):
count = 0
for n in numbers:
if is_even(n):
count += 1
return count
💡 This is composition — building bigger logic from smaller ones.
8️⃣ Default Parameters
def greet(name="Guest"):
print("Hello", name)
Usage:
greet()
greet("Amit")
Default values make functions flexible.
9️⃣ Breaking Problems into Functions (Key Skill)
Example Problem
Given a list of numbers, count even numbers.
Bad Thinking
Write everything in one block.
Good Thinking
🧠 Functions = units of thinking
⚠️ Common Beginner Mistakes
🧪 Practice Questions (Think First)
Q1
Write a function that takes two numbers and returns the larger one.
Q2
Write a function that returns whether a number is positive, negative, or zero.
Q3
Write a function that takes a list and returns the sum of elements.
Q4
Write a function that counts vowels in a string.
Q5
Write a function that checks if a number is prime.
Q6
Write a function that reverses a string.
Q7 (Thinking Question)
Why is returning values better than printing them inside functions?
Answer in words.
🔑 HINTS (Read Together, Only If Stuck)
✅ What You Should Be Able to Do Now
After Day 4, you should:
🧠 Reflection Questions (Answer in Words)
⭐ Golden Rule from Day 4
Good programmers don’t write more code. They write better-structured code.
If you say “Continue with Day 5”, next we’ll cover:
Ready when you are.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.