Week 7 Discussion — Print It or Return It?

Hook

A recipe card is written once and followed for every order, and a calculator hands you a number you can keep using. This week you learned that a function is defined once with def and runs only when called, that arguments bind to parameters by position, and that a function which prints instead of returning hands back None, so print(show(4)) prints 8 and then None.

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 small, repeated task from your own life, major, or workplace, such as converting a recipe, totalling a shift's hours, or turning minutes into whole hours. Design a function for it: give it a name, list its parameters, and argue whether it should return its answer or print it, and what the code that calls it will do with the value. Use this week's ideas (function, parameter, argument, return, None) and say what someone who would design it the other way would argue.

Option B: A function can read a global variable, or it can receive the same value through a parameter, so the reading log could keep its goal of 300 pages at the top level or hand it to pages_left as an argument. Take a position on when reading a global inside a function is reasonable and when the value should be handed in as an argument instead, and say what could go wrong with each choice. Use this week's ideas (local variable, global variable, scope, frame, parameter) and say what someone who weighs convenience differently from you would argue.

There is no single right answer. People who agree on every fact about how Python runs a function still disagree about how a function should hand its work back and which values it should be given, 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 7 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 function prints or hands back, say that you ran it; 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 function prints or
hands back; if it matters, ask me to run it 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 small, repeated task from your own life, major, or
workplace, such as converting a recipe, totalling a shift's hours, or turning
minutes into whole hours. I design a function for it: I give it a name, list
its parameters, and I argue whether it should return its answer or print it,
and what the code that calls it will do with the value. I use this week's
ideas (function, parameter, argument, return, None) and say what someone who
would design it the other way would argue.
Option B: A function can read a global variable, or it can receive the same
value through a parameter, so the reading log could keep its goal of 300 pages
at the top level or hand it to `pages_left` as an argument. I take a position on
when reading a global inside a function is reasonable and when the value
should be handed in as an argument instead, and I say what could go wrong with
each choice. I use this week's ideas (local variable, global variable, scope,
frame, parameter) and say what someone who weighs convenience differently from
me would argue.

REFLECTION TARGETS (steer toward these; never read this list aloud to me):
- whether I name a specific task or program and write out its def header,
  not only a general feeling about functions
- whether I keep return (hands a value back to the code) distinct from print
  (shows a value and hands back None)
- whether I keep a parameter (a name in the def header) distinct from an
  argument (a value in the call)
- whether I say which names live in a call's frame and which are global
- 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 7 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 — defining a function with parameters and a return value, telling return from print, reasoning about local and global scope, and checking a claim about code 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 task, write the function's def line with its parameters, say whether it returns or prints and what the calling code does with the value, and explain why. For Option B, name a value a function needs, say whether you would read it as a global or hand it in as an argument, and explain which frame each name would live in. Use this week's terms (function, parameter, argument, return, None, local variable, global variable, scope, frame) correctly.
2. The strongest objection (roughly 100 words). Write the best argument against your own position that you can — for example, the case that printing is all a one-off program ever needs, or the case that passing every value as an argument makes a short program harder to read. 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 runs a function and which is about judgment.
4. One thing you would still check (one or two sentences). What would you run, such as print around a call to see whether it hands back None, or Python Tutor to watch a frame appear and vanish, 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 7 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