Your First Week
A look back at what you built this week — and a glimpse of what's coming next.
Your First Week
Five days ago, you didn't know what def meant.
That's not an exaggeration. On Day 2, the opening quiz asked you what def does in Python, and there's a good chance you guessed. You might have confused print with return. The word "boolean" probably sounded like a made-up thing. range(5) producing 0 through 4 instead of 1 through 5? Nonsensical.
Look at where you are now.
On Day 3, you wrote your first function. One line of real Python — return True — and it worked. The computer did exactly what you told it to do. It wasn't magic. It was just text in a file, and Python followed your instructions.
On Day 4, your functions learned to accept input. You gave make_greeting a name, and it gave you back a personalized message. Parameters, arguments, return values — the vocabulary that felt foreign on Monday became the tools you used on Tuesday.
On Day 5, you stopped wrestling with + and str() and discovered f-strings. Suddenly, building formatted output felt natural. You took raw data — an item name, a quantity, a price — and turned it into a clean receipt line. You chained string methods like an assembly line: strip the spaces, capitalize the words, check for the @ sign.
On Day 6, your code started making decisions. if, elif, else — the same logic you've been writing in spreadsheet IF formulas, but without the nesting nightmare. You wrote a grading function that takes a number and returns a letter, and it handled every edge case correctly on the first try.
On Day 7, your code learned to repeat. A for loop took a list of numbers and summed them up, one at a time, using the accumulator pattern. You went from processing one piece of data to processing an entire list — the same list that would have taken you 200 manual steps in a spreadsheet.
That's the arc of this week: from "what is Python" to "I wrote a function that takes input, makes decisions, and repeats." You didn't just learn syntax. You learned to think in small, composable steps — define a function, give it inputs, return a result, repeat for every item.
But here's the thing. Right now, every piece of data you've worked with has been typed directly into your code. A list of five names. A single score. One receipt item. What happens when you have a thousand customers? Ten thousand rows of sales data? A CSV file someone emailed you at 4 PM with "can you get me a summary by end of day"?
That's Week 2. Your programs are about to get smarter — and your data is about to get bigger.
Practice your skills
Sign up to write and run code in this lesson.
Your First Week
A look back at what you built this week — and a glimpse of what's coming next.
Your First Week
Five days ago, you didn't know what def meant.
That's not an exaggeration. On Day 2, the opening quiz asked you what def does in Python, and there's a good chance you guessed. You might have confused print with return. The word "boolean" probably sounded like a made-up thing. range(5) producing 0 through 4 instead of 1 through 5? Nonsensical.
Look at where you are now.
On Day 3, you wrote your first function. One line of real Python — return True — and it worked. The computer did exactly what you told it to do. It wasn't magic. It was just text in a file, and Python followed your instructions.
On Day 4, your functions learned to accept input. You gave make_greeting a name, and it gave you back a personalized message. Parameters, arguments, return values — the vocabulary that felt foreign on Monday became the tools you used on Tuesday.
On Day 5, you stopped wrestling with + and str() and discovered f-strings. Suddenly, building formatted output felt natural. You took raw data — an item name, a quantity, a price — and turned it into a clean receipt line. You chained string methods like an assembly line: strip the spaces, capitalize the words, check for the @ sign.
On Day 6, your code started making decisions. if, elif, else — the same logic you've been writing in spreadsheet IF formulas, but without the nesting nightmare. You wrote a grading function that takes a number and returns a letter, and it handled every edge case correctly on the first try.
On Day 7, your code learned to repeat. A for loop took a list of numbers and summed them up, one at a time, using the accumulator pattern. You went from processing one piece of data to processing an entire list — the same list that would have taken you 200 manual steps in a spreadsheet.
That's the arc of this week: from "what is Python" to "I wrote a function that takes input, makes decisions, and repeats." You didn't just learn syntax. You learned to think in small, composable steps — define a function, give it inputs, return a result, repeat for every item.
But here's the thing. Right now, every piece of data you've worked with has been typed directly into your code. A list of five names. A single score. One receipt item. What happens when you have a thousand customers? Ten thousand rows of sales data? A CSV file someone emailed you at 4 PM with "can you get me a summary by end of day"?
That's Week 2. Your programs are about to get smarter — and your data is about to get bigger.
Practice your skills
Sign up to write and run code in this lesson.