Five functions, all working on the same client list. filter_active_clients, compute_totals_per_client, find_first_over_budget, group_by_status, status_summary. Which one felt like the biggest leap from Week 1?
status_summary — loops inside loops. I had to slow down and trace the data shape before I could write it.
That is the right instinct. Nested structures reward you for drawing the shape on paper first. Which Day 1 concept from last week kept showing up this week?
is_over_hours logic — the > comparison I wrote on Day 6 reappeared everywhere: filter, while loop, status grouping. It was already doing work without me realising.
Functions that compose without planning. That is the real payoff. Let's check what stuck.
Six questions. Ready.
All from this week's code. Two from Week 1 to keep the earlier patterns warm.
Five functions, all working on the same client list. filter_active_clients, compute_totals_per_client, find_first_over_budget, group_by_status, status_summary. Which one felt like the biggest leap from Week 1?
status_summary — loops inside loops. I had to slow down and trace the data shape before I could write it.
That is the right instinct. Nested structures reward you for drawing the shape on paper first. Which Day 1 concept from last week kept showing up this week?
is_over_hours logic — the > comparison I wrote on Day 6 reappeared everywhere: filter, while loop, status grouping. It was already doing work without me realising.
Functions that compose without planning. That is the real payoff. Let's check what stuck.
Six questions. Ready.
All from this week's code. Two from Week 1 to keep the earlier patterns warm.