Lists: Operations & Slicing

Discussion prompt

Before we open Lists: Operations & Slicing: without looking back, what was the main idea of Data Types & Conversion, and what could you do by the end of it that you could not do before?

Hint: One sentence for the idea, one for the skill. If the second one is blank, that is the part to revisit.

Comparison matrix

From Why lists matter at camp: refill the What it looks like column from what you know. The rest of the table is as it appeared.

Discussion prompt

[10, 20, 30, 40] is a list of four numbers. ["Bolt", "Ace"] is a list of two strings. Order matters - the list remembers exactly where everything sits.

That is stated as though it always holds. Do one of two things: produce a case where it fails, or say precisely what rules such a case out. "It just does" is not on the menu.

Hint: Hunt at the extremes first — zero, one, negative, empty, equal. If every extreme survives, the reason they survive is the proof.

Discussion prompt

Explain Lockers numbered from 0 by analogy to something with no Python in it at all — a queue, a recipe, a map, a bank balance, whatever fits. Then say where your analogy breaks.

Hint: An analogy that never breaks is not an analogy, it is the same idea wearing a hat. Find the seam — that is the part that is actually new.

Discussion prompt

Explain Indexing: grab one item to a student a year behind you. No notation, no jargon they have not met — and it still has to be true.

Hint: If your explanation needs a symbol they have never seen, you are describing the notation rather than the idea.

Put in order

Put the moves of Grabbing heroes by index into the order they have to happen.

1. Read squad[0]
2. Read squad[2]
3. Read squad[5]

Why: These are the moves of the worked example in the order it makes them, and each one is set up by the one before it. Count lockers 0, 1, 2 - that lands on Nova, the THIRD hero.

Comparison matrix

From Grabbing heroes by index: every row here is a choice with a cost. Fill the locker column, then say which row you would actually pick and what you give up for it.

Predict first

A student writes this, and it looks reasonable:

"I want the first hero, so I write squad[1]."

It is wrong. Say what breaks — and say it before you turn the page.

Correct: Feels right - first item, number 1.

"The painter started at 0, so the first locker is squad[0]."

Why: Feels right - first item, number 1. But Python hands back Ace, the second hero.

Draw it

Draw what The last hero, no counting needed just did — the shape of it, not the line-by-line working. One picture, labels only where you need them. Then check it against the steps: anything you could not draw is a step you followed rather than understood.

Discussion prompt

Read the picture before the words. What is this showing, and what is the one thing it is built to make obvious? Commit to an answer, then read on.

Hint: Name the parts, then say what changes between them — and if nothing changes, say what is being held still.

Predict first

The table runs: print(nums[0]) | 10 | single item at locker 0 · print(nums[1:3]) | [20, 30] | indexes 1 and 2 - end excluded

In Tracing nums[1:3], given the rows so far: what is the next one — the row where line is items in the slice?

Correct: items in the slice | 2 | 3 - 1 = 2

Why: The relationship between the columns, not the individual numbers, is what generates the next row. Plain index - locker 0 holds 10.

Annotate

Walk the callouts on Tracing nums[1:3]. Each one is a place this is easy to get subtly wrong.

• Plain index - locker 0 holds 10. No brackets in the output: one item, not a list.
• Start at index 1 (the 20), stop BEFORE index 3 (the 40). Items 1 and 2 come along - the 40 stays behind.

Predict first

A student writes this, and it looks reasonable:

"nums[1:3] means items 1 through 3, so I get [20, 30, 40] - three items."

It is wrong. Say what breaks — and say it before you turn the page.

Correct: Reads like a range of lockers from 1 to 3 - but Python stops at the second cut, and 40 never makes it in.

"nums[1:3] means start at 1, stop BEFORE 3 - so I get [20, 30] - two items."

Why: Reads like a range of lockers from 1 to 3 - but Python stops at the second cut, and 40 never makes it in.

Discussion prompt

The rule this trap just fixed:

The end number is the stop sign, not a passenger. Count check: 3 - 1 = 2 items.

Now break it on purpose. Build a case that violates it and follow the consequences until something visibly fails. Where does the failure first show up — and would you have noticed it if you had not been looking?

Hint: The dangerous rules are the ones whose violation still produces an answer. If yours fails loudly, try to find one that fails quietly.

Draw it

Draw what Shortcuts in action just did — the shape of it, not the line-by-line working. One picture, labels only where you need them. Then check it against the steps: anything you could not draw is a step you followed rather than understood.

Fill in the blanks

From Merging two squads — one line has had its right-hand side removed. Put it back.

squad = ["Bolt", "Ace", "Nova", "Rex", "Zap", "Pixel"]
squad2 = ["Turbo", "Glitch"]
team = squad + squad2
print(team)
print(len(team))

Why: team is what everything below it consumes, so the wrong expression here fails later and somewhere else. All six originals first, then the two recruits, in order - a brand-new 8-item list.

Annotate

Walk the callouts on Merging two squads. Each one is a place this is easy to get subtly wrong.

• All six originals first, then the two recruits, in order - a brand-new 8-item list.
• 6 + 2 = 8. Joining lists adds their LENGTHS, never the items inside.

Predict first

A student writes this, and it looks reasonable:

"Plus means add, so [1, 2] + [3] is 1 + 2 + 3 = 6."

It is wrong. Say what breaks — and say it before you turn the page.

Correct: That is what + does to plain numbers - but these are lists, and + never opens the boxes to do math.

"These are lists, so + glues them: [1, 2] + [3] is [1, 2, 3]."

Why: That is what + does to plain numbers - but these are lists, and + never opens the boxes to do math.

Predict first

The table runs: ["Go!"] * 3 | ['Go!', 'Go!', 'Go!'] · [1, 2] * 2 | [1, 2, 1, 2]

In The chant builder, given the rows so far: what is the next one — the row where expression is **[0] * 3**?

Correct: [0] * 3 | [0, 0, 0]

Why: The relationship between the columns, not the individual numbers, is what generates the next row. One copy, two copies, three copies, glued into a single list of 3 items.

Comparison matrix

From The chant builder: refill the result column from what you know. The rest of the table is as it appeared.

Predict first

A student writes this, and it looks reasonable:

"Times 3 multiplies, so [0] * 3 is [0]... and [1, 2] * 2 must be [2, 4]."

It is wrong. Say what breaks — and say it before you turn the page.

Correct: Feels like math class - but * on a list never touches the numbers inside the brackets.

"* copies the whole list: [0] * 3 is [0, 0, 0] and [1, 2] * 2 is [1, 2, 1, 2]."

Why: Feels like math class - but * on a list never touches the numbers inside the brackets.

Sort into buckets

Some of these hold up and some are the exact mistakes this lesson is built to prevent. Sort them.

Holds up

Sensor readings, color channels, and motor commands almost always travel in lists - a robot is basically a machine that reads lists and writes lists.; [10, 20, 30, 40] is a list of four numbers. ["Bolt", "Ace"] is a list of two strings. Order matters - the list remembers exactly where everything sits.; Picture the squad in a row of lockers. Python paints a number on every locker - but the painter starts at 0, not 1.

Breaks

"I want the first hero, so I write squad[1]."; "nums[1:3] means items 1 through 3, so I get [20, 30, 40] - three items."

sound

These are stated as this lesson states them — each one survives the edge cases Lists: Operations & Slicing puts it through.

flawed

Each of these is lifted from a trap in this deck: reasonable-sounding, and wrong in a way that only shows up once you rely on it.

Discussion prompt

Explain Lists can change: swap an item to a student a year behind you. No notation, no jargon they have not met — and it still has to be true.

Hint: If your explanation needs a symbol they have never seen, you are describing the notation rather than the idea.

Fill in the blanks

From Trading Ace for Comet — one line has had its right-hand side removed. Put it back.

squad = ["Bolt", "Ace", "Nova", "Rex", "Zap", "Pixel"]
squad[1] = "Comet"
print(squad)

Why: squad[1] is what everything below it consumes, so the wrong expression here fails later and somewhere else. Index 1 held Ace; the assignment replaces just that one slot, everyone else stays put.

Match the pairs

Match each term to the definition this lesson gave it — not the one you would guess from the word.

• t1. list
• t2. index
• t3. slice
• t4. concatenation
• t5. append

• d1. An ordered collection of values, written between square brackets and separated by commas.
• d2. An item's position number in a list, starting from 0. Written in square brackets after the list's name: squad[0].
• d3. list[start:end] - a NEW list containing the items from index start up to, but NOT including, index end.
• d4. Gluing two lists end-to-end with + to make one NEW, longer list.
• d5. list.append(item) adds one item to the END of the list, in place - the list itself gets longer.

Why: These are the working definitions of list, index, slice, concatenation, append as Lists: Operations & Slicing uses them. Pairing them correctly is the test of whether you could state each one with the slide switched off.

Discussion prompt

Outside this lesson: where does Lists: Operations & Slicing actually turn up? Name one concrete situation — a job, a piece of software someone ships, a decision somebody has to make — and say which part of The list toolbox is doing the work in it.

Hint: Vague is the failure mode here. "Engineering" is not a situation; "deciding whether this build is fast enough to ship" is.

Check your understanding

What does print(squad[1]) show?

• A. Bolt
• B. Ace (correct)
• C. Nova
• D. an IndexError

Answer: B

Why: Indexes start at 0, so locker 0 holds Bolt and locker 1 holds Ace - squad[1] is the SECOND hero.

Why A tempts people

Treats 1 as the first position - but Python starts counting at 0, so the first hero is squad[0].

Why C tempts people

Counted two steps in (lockers 1 and 2) instead of reading locker 1 directly.

Why D tempts people

1 is a perfectly valid index here - errors only happen past the end, like squad[6].

Check your understanding

What does print(nums[1:3]) show?

• A. [20, 30, 40]
• B. [10, 20, 30]
• C. [20, 30] (correct)
• D. [30]

Answer: C

Why: Start at index 1 (the 20), stop BEFORE index 3 - so only indexes 1 and 2 come along. Count check: 3 - 1 = 2 items.

Why A tempts people

Included the end index 3 - but the end is the stop sign, and the 40 never makes it in.

Why B tempts people

Started counting positions at 1 instead of 0, taking the 'first through third' items.

Why D tempts people

Took only the item at the end index minus... this keeps one item, but a [1:3] slice spans two lockers.

Check your understanding

What does print([1, 2] + [3]) show?

• A. 6
• B. [1, 2, 3] (correct)
• C. [4, 5]
• D. an error

Answer: B

Why: + between two lists glues them end-to-end into one new list: [1, 2, 3]. It never does arithmetic on the items inside.

Why A tempts people

Added the numbers inside (1+2+3) - but + on lists joins the boxes, it never opens them.

Why C tempts people

Added 3 to each item - that elementwise math is something + on plain lists never does.

Why D tempts people

Joining two lists with + is completely legal - the error comes from mixing types, like [1, 2] + 3 without brackets.

Check your understanding

What does print([0] * 3) show?

• A. [0]
• B. 0
• C. [0, 0, 0] (correct)
• D. [3]

Answer: C

Why: * repeats the whole list: three stamps of [0] make [0, 0, 0]. The length multiplies; the values inside never change.

Why A tempts people

Multiplied the inside: 0 x 3 = 0, list unchanged - but * never touches the items, it copies the list.

Why B tempts people

Did plain number math 0 x 3 - but one side is a list, so the result is a longer list, not a number.

Why D tempts people

Multiplied 0... wait, replaced the item with 3 - * never rewrites items, it only repeats the pattern.

Eliminate the wrong options

team has 8 items. How many items are in team[2:5]?

3 of these 4 are wrong. Strike them one at a time, and say what rules each one out before you strike the next. The survivor is the answer.

• A. 4
• B. 3
• C. 2
• D. 5

Survives elimination: B

Why: A slice holds end minus start items: 5 - 2 = 3 (indexes 2, 3, and 4 - the 5 is excluded).

Check your understanding

team has 8 items. How many items are in team[2:5]?

• A. 4
• B. 3 (correct)
• C. 2
• D. 5

Answer: B

Why: A slice holds end minus start items: 5 - 2 = 3 (indexes 2, 3, and 4 - the 5 is excluded).

Why A tempts people

Counted 2 through 5 inclusive (2, 3, 4, 5) - but the end index never comes along.

Why C tempts people

Subtracted an extra one, as if BOTH ends were excluded - the start index IS included.

Why D tempts people

Read the end index as the count - the slice stops at 5, it does not contain 5 items.

Discussion prompt

Explain PROJECT: Dream Team Roster by analogy to something with no Python in it at all — a queue, a recipe, a map, a bank balance, whatever fits. Then say where your analogy breaks.

Hint: An analogy that never breaks is not an analogy, it is the same idea wearing a hat. Find the seam — that is the part that is actually new.

Comparison matrix

From Build it 3: merge the recruits - your turn: every row here is a choice with a cost. Fill the expected column, then say which row you would actually pick and what you give up for it.

Comparison matrix

From Build it 4 (stretch): captain, bench, chant: refill the what prints column from what you know. The rest of the table is as it appeared.

Predict first

If yours prints your own six heroes in the same shape - you built it. Different names, same superpowers.

Commit before you compute: what does The whole roster program come out to? A rough magnitude and the right form is enough — the point is to have something concrete to be wrong about.

Correct: Read the program top to bottom

Why: A prediction you can defend turns the computation into a check rather than a leap of faith — and an answer that contradicts it is caught on the spot. Draft the squad, slice the starters, merge the recruits, then index, slice, and stamp - every tool from the hour in nine lines.

Discussion prompt

Work backwards. The example finished here:

Read the program top to bottom

What was it asked to do, and what must it have been given? Reconstruct the problem from its answer.

Hint: Every quantity in the result had to enter somewhere. Account for each one.

Discussion prompt

Last 5 minutes: run your roster and explain it line by line - what [:3] grabs and why the end index stays out, why + made the team longer but never did math, and what * 3 stamped out.

That is stated as though it always holds. Do one of two things: produce a case where it fails, or say precisely what rules such a case out. "It just does" is not on the menu.

Hint: Hunt at the extremes first — zero, one, negative, empty, equal. If every extreme survives, the reason they survive is the proof.

Draw it

One page, no notation unless you need it: draw how these connect — The list toolbox · Why lists matter at camp · What a list is · Lockers numbered from 0 · Indexing: grab one item. Put an arrow wherever one of them is what makes another possible, and label the arrow with why.