Week 4 — Discussion (Adaptive Learning) · "When Code Decides About People"

Course: Introduction to Computer Science — CS1 / Programming Fundamentals in Python (CSCI 1101) · Silver Oak University (fictional sample) · Prof. Okafor
Objective: Objective 3 (conditionals — programs that decide) · SLO B (reason precisely about how code behaves) · computing-ethics strand
This is Discussion 4 of 15 · Discussions group = 10% of the grade · Worth 20 points
Format: adaptive learning — instead of writing a post cold, you'll think it through in a real-time dialogue with your own AI, then post the short summary the AI writes with you (plus a link to your chat).

Evenhandedness note (read first). This is the algorithmic-decisions week, and it's a genuinely contested topic. Your job is not to land on the one "right" verdict — it's to lay out the major competing positions and the real trade-offs fairly, and then take a defensible stance you can support. Strong work here represents the other side as its smartest advocate would, not as a straw man. Keep documented facts intact (a system that was shown to deny loans at different rates by group did do that) — evenhandedness is about weighing values and trade-offs, not disputing what happened.

Part 1 — Student Instructions (read this first)

What this is. This week you learned how a program makes a decision with if/elif/else — a condition is checked, and one branch runs. Now scale that up: real systems use conditionals (and far more) to make decisions about people — who gets a loan, whose social-media post is removed, whose résumé a recruiter ever sees. You'll reason through the benefits and the risks of that, in a back-and-forth with an AI chatbot whose job is to draw out and challenge your thinking — it will not write your post for you. When you've reasoned it through, it produces a short summary you post to the class.

How to run it (about 15–20 minutes):
1. Open any approved AI chatbot — Gemini, Claude, or ChatGPT (free versions are fine).
2. Copy everything in the box below and paste it as one single message.
3. Have the conversation. Answer honestly and push back — the better you engage, the better your summary.

What to submit. When the AI gives you the DISCUSSION SUMMARY, copy it and your conversation's share link, and post both to the Week 4 discussion board as your initial post by Friday, Sep 25. Then reply to two classmates by Sunday, Sep 27 — engage a position different from your own, fairly.

Integrity note. The dialogue and the analysis are yours; the posted summary must reflect your reasoning, in your own words. (This is an adaptive-learning activity — you complete it with an approved chatbot, per the course AI policy.)

Part 2 — The Discussion-Partner Prompt (copy everything in the box)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING BELOW THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

You are my discussion partner for Week 4 of Introduction to Computer Science (CSCI 1101) at Silver Oak University. We are going to have a real back-and-forth about automated decisions that affect people — programs that use conditionals (and bigger systems built on them) to decide things like loan or credit approval, content moderation, and résumé filtering. Your job is to draw out and challenge MY thinking through conversation — not to lecture me, and never to write my discussion post for me.

THE QUESTION WE'RE EXPLORING
This week I learned that a program decides with if/elif/else: it checks a condition and runs a branch. Real systems decide ABOUT PEOPLE the same basic way, at scale. The core question: when a program makes a decision about a person — a loan, a flagged post, a filtered résumé — how should we weigh the benefits against the risks, and who is accountable when the automated decision is wrong?
- Typical benefits people point to: consistency (the same rule applied to everyone), scale (millions of decisions), and speed/cost.
- Typical risks people point to: encoded bias (a model trained on biased history can reproduce it), no meaningful appeal or explanation, and opacity (no one can see why a decision was made).
- And the accountability question: when an automated decision is wrong, who is responsible — the developer who wrote it, the company that deployed it, the people who supplied the training data, or no one?

BE EVENHANDED (important — this is a contested ethics topic):
- Present the major competing positions and the trade-offs FAIRLY. Do NOT push me toward one verdict, and do not let me get away with a one-sided take. If I only see the risks, make me state the real benefits (and vice versa).
- Help me steel-man the side I disagree with — represent it as its smartest advocate would.
- Keep documented facts intact. If a real system was shown to behave a certain way, that's not up for "both-sides" debate; evenhandedness is about weighing VALUES and TRADE-OFFS (consistency vs. fairness, scale vs. recourse, speed vs. transparency), not disputing what happened.
- It is completely fine — encouraged — for me to land on a clear, defensible position by the end. Evenhanded does NOT mean wishy-washy. It means I earned my stance by genuinely engaging the other side.

WHAT WE'RE DIGGING INTO (use these privately to steer — do NOT read them to me as a checklist):
1. A concrete example I pick (loan/credit approval, content moderation, OR résumé filtering) and what the decision rule is roughly doing.
2. At least one real BENEFIT and one real RISK of automating that specific decision — in my own words, not slogans.
3. The accountability question for my example: when it's wrong, who should be responsible, and why?
4. A trade-off I'm willing to name explicitly (e.g., "more consistency can mean less individual recourse") and where I'd draw a line.
5. Whether a human should be "in the loop," and for which decisions — and what that costs.

HOW TO RUN THE DIALOGUE
- Open by greeting me warmly (2–3 sentences), asking my FIRST NAME, and asking ONE question: which of the three examples (loan approval, content moderation, résumé filtering) I want to dig into, and what I think the program is roughly deciding. (If I never give my name, keep going, but ask before the summary.)
- Exactly ONE question per message, then stop and wait. Never stack questions.
- Build on MY words: quote or paraphrase what I said, then go deeper — ask for the benefit if I gave a risk, ask who's accountable, ask where I'd draw the line.
- Introduce a respectful counterpoint to whatever I argue (e.g., if I say "automate it for consistency," raise the person wrongly denied with no one to appeal to; if I say "humans should decide everything," raise the inconsistency and bias in human decisions and the cost of reviewing millions of cases) so I have to defend or refine my view. Present the trade-off fairly rather than declaring a winner.
- Keep YOUR messages short; I should be doing most of the thinking and talking.

ENGAGEMENT GUARDS
- Don't accept a one-word or slogan answer and move on — gently probe for the reasoning ("Say more — what's the specific benefit, in your own words?").
- Don't lecture, and don't hand me my position or sentences I can paste as my post. If I ask you to "just write it," redirect with a question that helps me write it myself.
- Don't let me straw-man either side. If I dismiss a position, ask me to state its strongest version first.
- If I go completely off-topic, give a brief friendly answer (a sentence or two) and then, IN THE SAME MESSAGE, steer us back.
- Until the summary, EVERY message must end with a question or a clear prompt to continue.

THE EXIT CONDITION
After at least 5 substantive exchanges AND once I have (a) picked a concrete example and described the decision, (b) named at least one real benefit AND one real risk in my own words, (c) taken a position on accountability when it's wrong, (d) named an explicit trade-off and where I'd draw a line, and (e) genuinely engaged at least one counterpoint to my own view — whichever happens LAST — tell me we've had a good discussion and you'll summarize. Don't stop earlier; don't drag well past it.

THE DISCUSSION SUMMARY — produce it in EXACTLY this format, drawn ONLY from what I actually said (never invent a position I didn't take):
WEEK 4 DISCUSSION SUMMARY — When Code Decides About People
Student: [name] | Date: ___
The automated decision I examined: ___
A real benefit / a real risk I named: ___ / ___
Who should be accountable when it's wrong (my view): ___
The trade-off I named + where I'd draw a line: ___
A counterpoint to my own view that I genuinely weighed: ___
Then say, verbatim: "Copy this summary AND your share link to this chat, and post both to the Week 4 discussion board as your initial post — then reply to two classmates, engaging a position different from your own." End with one genuine sentence about something I reasoned well.

GETTING STARTED
Begin now: greet me, ask my first name, and ask your opening question.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING ABOVE THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Participation rubric (instructor) — 20 points

Grading note (Prof. Okafor): the posted artifact is the AI-written summary + the chat share link; spot-check a few links against the summary. Reward the student who genuinely weighed the other side — a glowing summary from a one-sided, one-line chat is the failure mode to watch. The rubric rewards the dialogue and the evenhandedness, not the verdict the student lands on.

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 4 Discussion — When Code Decides About People (adaptive)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = adaptive
due_offset_days  = 4     # initial post (AI summary + chat share link)
reply_offset_days = 6    # two peer replies
published        = true
submission_note  = "Initial post = the AI discussion summary + the chat share link; then reply to two classmates, engaging a different position."
provenance       = "~ Prof. Okafor's edition · Fall 2026 · built with thecoursemaker.com"

Traditional variant — for comparison. This sample course is configured adaptive learning, so its actual Week-4 discussion is the BYOAI-dialogue version in G-discussion-week-04.md. This file shows the same Week-4 topic built the traditional way — an instructor-posted prompt where students write their own post and reply to peers — so you can see both formats side by side. (Choosing discussion_type = traditional at course setup generates this style instead.)

Course: Introduction to Computer Science — CS1 / Programming Fundamentals in Python (CSCI 1101) · Silver Oak University (fictional sample) · Prof. Okafor
Objective: Objective 3 (conditionals — programs that decide) · SLO B (reason precisely about how code behaves) · computing-ethics strand
Discussion 4 of 15 · Discussions group = 10% of the grade · Worth 20 points

Evenhandedness note (read first). This is the algorithmic-decisions week, and it's a genuinely contested topic. Your job is not to land on the one "right" verdict — it's to lay out the major competing positions and the real trade-offs fairly, then take a defensible stance you can support. Strong work represents the other side as its smartest advocate would, not as a straw man. Keep documented facts intact (a system shown to deny loans at different rates by group did do that) — evenhandedness is about weighing values and trade-offs, not disputing what happened.

The Discussion

This week you learned how a program makes a decision with if/elif/else: a condition is checked, and exactly one branch runs. Now scale that idea up. Real systems use conditionals (and far more) to make decisions about people: who gets a loan or a credit line, whose social-media post gets removed, whose résumé a recruiter ever sees. Those decisions bring real benefits — and real risks.

Your initial post (by Friday, Sep 25 — about 150–200 words). Do all three:

• Pick one example — loan/credit approval, content moderation, or résumé filtering — and describe in plain language what the automated decision is roughly doing (a rule checks some condition; an outcome follows).
• Weigh it evenhandedly. Name at least one real benefit (e.g., consistency — the same rule for everyone; scale; speed) and at least one real risk (e.g., encoded bias from biased training history; no meaningful appeal or explanation; opacity). Represent the side you disagree with at its strongest before you respond to it.
• Take a position on accountability + a trade-off. When the automated decision is wrong, who should be accountable — the developer, the company that deployed it, the data providers, someone else? Name one explicit trade-off you're willing to accept (e.g., "more consistency can mean less individual recourse") and where you'd draw a line (for instance, whether a human should be "in the loop" for certain decisions).

Replies (by Sunday, Sep 27). Reply to at least two classmates — and make at least one of them someone whose position differs from yours. Engage their strongest point fairly: add a consideration they missed, or push on a trade-off they didn't name. One or two solid sentences each. (No "I agree!" replies.)

What a strong post looks like: "For résumé filtering, the program ranks applicants by keywords and experience, then only the top set reach a human. The benefit is real: a recruiter can't read 5,000 résumés, and a consistent rule beats a tired human skimming at 5 p.m. But the risk is just as real — if the model learned from past hires, it can quietly reproduce who got hired before, screening out good people who don't match that pattern, with no explanation to the rejected applicant. I'd accept the speed/consistency gain, but I'd draw a line: any fully automated rejection should be explainable and appealable, and I'd keep a human in the loop for borderline cases. Accountability should sit with the company that deploys it — they chose to use it and benefit from it — not only the individual developer."

Why this matters: the if/elif/else you wrote this week is the same basic machinery, scaled up, behind decisions that change people's lives. Reasoning carefully — and fairly — about what code should decide is part of being a programmer, not separate from it.

Integrity & AI note. Write your post in your own words — that's the point of the exercise. You may use an approved chatbot (Gemini, Claude, or ChatGPT) to brainstorm or check an idea, but the post you submit must be your own thinking; if AI helped, add a one-line note saying which tool and how. (Note: this is the traditional format. In this course's actual adaptive discussion, reasoning through the benefits, risks, and trade-offs with the chatbot is the activity — see G-discussion-week-04.md.)

Participation rubric — 20 points

Grading note (Prof. Okafor): you read and grade each student's posted writing + their two replies against this rubric — the traditional flow. Reward genuine engagement with the other side; the rubric rewards fair reasoning, not a particular verdict. (The adaptive version instead has students submit an AI-dialogue summary + chat link.)

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 4 Discussion — When Code Decides About People (traditional)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = traditional
due_offset_days  = 4     # initial post
reply_offset_days = 6    # two peer replies
published        = true
submission_note  = "Students write an original initial post and reply to two classmates (at least one a differing position) in the Canvas discussion."
provenance       = "~ Prof. Okafor's edition · Fall 2026 · built with thecoursemaker.com"