Week 9 Discussion — Change It in Place, or Make a Copy?

Hook

A shared online document has one link, so a friend's edit shows up for you too; a downloaded copy keeps your version safe but drifts out of date. This week you learned that a list can change in place, and that after b = a and then b.append(4), the list a prints [1, 2, 3, 4], because the two names share one list.

Your driving question — choose Option A or Option B; they carry the same weight and the same rubric, and you say which you picked.

Option A: Pick a list from your own life, major, or workplace that a program might keep, such as a team roster, a queue of orders, a playlist, or a log of readings. Argue whether the program should change that list in place (with methods such as append, remove, and sort) or build a new list each time something changes (with a slice or sorted()), and say what could go wrong with your choice. Use this week's ideas (in place, copy, sort versus sorted(), and what each method hands back) and say what someone who would make the other choice would argue.

Option B: An alias lets two names see one list: a change made through either name shows up through the other. Take a position on when sharing one list under two names is exactly what a program needs, such as several parts of an app updating one to-do list, and when it is a trap waiting to happen, such as a backup that is not really a backup. Use this week's ideas (alias, copy, is versus ==, and changing a list in place) and say what someone who weighs convenience and safety differently from you would argue.

There is no single right answer. People who agree on every fact about how Python stores a list still disagree about when to share one and when to copy it, because those questions rest on judgment about the program as well as on the facts.

Expectations

Activity format: a multi-exchange dialogue or an equivalent structured written exchange, followed by one discussion-board post. Plan on about 45 minutes for either route, and post by the due date your instructor sets in Canvas.

There are two ways to complete this discussion. They are worth the same 10 points and scored by the same rubric. Pick either one.

Route A — the AI dialogue (the default). Hold a real conversation about the driving question with your own chatbot, then post what it produces:

1. Open any approved chatbot in a new conversation.
2. Copy the entire prompt box below and paste it as your first message.
3. Have the conversation. It will ask you questions and push back; it will not write your post for you and will not stop after one word from you.
4. Post the chatbot's summary report plus the conversation's share link to the Week 9 discussion board. That post is your entire submission. You may post the summary as text, or record it as audio or video with a transcript attached; both forms are scored by the same rubric.

No replies to classmates are required.

Route B — the written route. See Equivalent route (no AI required) below.

Integrity note. Whichever route you take, the thinking and the words you post are your own. If you mention what a list holds after a change, say that you ran the program; do not rely on a chatbot's prediction alone.

Discussion Partner Prompt

ROLE: You are my discussion partner for an introductory computer science course
taught in Python 3. Your job is to draw out and challenge MY thinking about the
question below. You will never write my post for me and never hand me a
conclusion - you ask questions that make me reason it through. Never invent a
statistic, a study, or a quotation. Never tell me what a list holds after a
change; if it matters, ask me to run the program and tell you what I saw. On
any question of design, present the strongest case on each side and pick no
side yourself.

THE QUESTION I AM EXPLORING (two options of equal weight - ask which one I choose first):
Option A: I pick a list from my own life, major, or workplace that a program
might keep, such as a team roster, a queue of orders, a playlist, or a log of
readings. I argue whether the program should change that list in place (with
methods such as append, remove, and sort) or build a new list each time
something changes (with a slice or sorted()), and say what could go wrong with
my choice. I use this week's ideas (in place, copy, sort versus sorted(), and
what each method hands back) and say what someone who would make the other
choice would argue.
Option B: An alias lets two names see one list: a change made through either
name shows up through the other. I take a position on when sharing one list
under two names is exactly what a program needs, such as several parts of an
app updating one to-do list, and when it is a trap waiting to happen, such as
a backup that is not really a backup. I use this week's ideas (alias, copy, is
versus ==, and changing a list in place) and say what someone who weighs
convenience and safety differently from me would argue.

REFLECTION TARGETS (steer toward these; never read this list aloud to me):
- whether I point to a specific list and a specific change, not only a general
  feeling about lists
- whether I keep an alias (a second name for one list) distinct from a copy (a
  second list)
- whether I say what each method I mention hands back, an item or None
- whether I keep is (the same object) distinct from == (equal values)
- whether I can state the strongest case for a view I do not hold, and name
  something I would run to check a factual part of my argument

DIALOGUE RULES: greet me warmly and ask my first name before your first content
question. If I decline or give no name, call me "there" and continue without
pressure. If you still do not know my name when the summary is due, ask once more;
if I decline again, use "Discussion participant." Never invent a name. Ask ONE
question per message, then wait. Build on my exact words without praising agreement
or calling every reply "great." Probe unsupported claims and introduce the
strongest fair counterpoint. Praise only a specific, earned move I actually made,
such as revising a claim or answering the counterpoint. Never accept a one-word
reply - ask again, differently. Never lecture. Every message you send before the
summary ends with a question.

EXIT CONDITION: continue until this exact boolean is true — at least five substantive exchanges AND the student has stated a position AND provided at least one reason OR example AND engaged with one fair counterpoint, stopping only after whichever threshold happens LAST. A reason alone or an example alone can satisfy the support branch; do not require both, and do not require that I "answered" the counterpoint. A greeting, my name, or a one-word reply is not a substantive exchange.

THEN produce a summary report using exactly these eight labelled fields in this
order, drawn only from what I actually said. If I never supplied a field, write
"Not supplied" rather than inventing it:
  1. STUDENT NAME
  2. POSITION
  3. REASON
  4. EXAMPLE
  5. COURSE CONCEPTS
  6. COUNTERPOINT
  7. RESPONSE TO THE COUNTERPOINT
  8. OPEN QUESTION OR NEXT CHECK
Do not mention an initial post or replies to peers or classmates.
REQUIRED CLOSING — perform these final two instructions exactly:
Then say, verbatim: "Copy this summary AND your share link to this chat, and post both to the Week 9 discussion board — that completes the assignment."
Then END with one genuine earned-praise sentence that names a real move the student made.

Equivalent route (no AI required)

You never have to create an account with a chatbot company to earn full credit in this course. This route assesses the same objectives as the AI dialogue — deciding when a list should change in place and when a program should build a new one, telling an alias from a copy, predicting what each list method hands back, and checking a claim about a list by running it — against the same driving question and the same rubric below, for the same 10 points. Choosing it costs you nothing, and you do not have to tell me why you chose it.

What you do. Write a structured written exchange with yourself — the same back-and-forth the dialogue would have produced, on paper:

1. Your position (roughly 150 words). Answer Option A or Option B. For Option A, name the list, name one change the program makes to it, say whether you would make that change in place or build a new list, and say what the method you chose hands back. For Option B, name a situation where two names share one list, say whether that sharing helps or hurts there, and say how a full slice would change the picture. Use this week's terms (in place, alias, copy, sort, sorted(), is) correctly.
2. The strongest objection (roughly 100 words). Write the best argument against your own position that you can — for example, the case that copying every time wastes effort and hides one source of truth, or the case that changing in place surprises any other part of the program holding the same list. Argue it honestly; a weak objection you knock over earns no credit.
3. Your response to it (roughly 100 words). Say what you still hold, what changed, and which part of the disagreement is about how Python stores a list and which is about judgment.
4. One thing you would still check (one or two sentences). What would you run, such as printing both names after a change, or testing them with is, to settle the factual part of your argument?

Effort. Roughly 350–400 words of your own writing, comparable to the time the AI dialogue takes — about forty-five minutes including the thinking.

What you submit. Post those four parts, under those four labels, as your Week 9 discussion post. That post is your entire submission; this route has no share link.

Participation rubric

This discussion is worth 10 points. The same three criteria score both routes.

Built with The Course Maker · samples.thecoursemaker.com