Week 11 Discussion — Text at Scale: Tidy It, Count It, or Leave It Alone? — Traditional alternative (no AI)
Instructors: publish this instead of the adaptive version if you prefer, and unpublish or delete the adaptive one.
Hook
A sign-up sheet full of Yes, yes, and YES looks like one answer to a person, and a few lines of Python can make it one answer to a program too. This week you learned that a string method hands back a new string and never changes the old one, that split makes a list and join makes a string, and that normalizing with strip and lower turns " Yes " into yes, so the comparison with "yes" goes from False to True. The same few lines run as easily over a pile of messages as over one.
Your discussion question — choose Option A or Option B; they carry the same weight and the same rubric, and you say which you picked.
Option A: A word-count program built from split and the counting idiom can tally every word in a group chat, a class forum, or a workplace channel in seconds. Pick one such setting from your own life, major, or workplace and take a position on whether, and under what limits, the group should run that kind of program over messages its members wrote. Use this week's ideas (split, string method, normalize, count) and say what someone who weighs privacy and usefulness differently from you would argue.
Option B: Normalizing with strip and lower makes typed text match when the differences do not matter, but some differences do matter: a capital letter in a name, the spacing in an address, or the exact characters of a password. Pick one kind of text a program you know collects and take a position on when that program should normalize it before comparing and when it should keep the text exactly as typed. Use this week's ideas (normalize, whitespace, string method, the forgot-to-reassign bug) and say what someone who weighs consistency and fairness differently from you would argue.
There is no single right answer. People who agree on every fact about what split, lower, and count hand back still disagree about when a program should run them over other people's words, because those questions rest on judgment about people as well as on the facts about Python. Pick the option you actually care about, and make your case.
Expectations
Activity format: one initial post followed by two substantive peer replies. Plan on about 45 minutes across the two deadlines; your instructor sets both due dates in Canvas.
Your initial post — by the first due date (early in the module week):
- Say which option you chose.
- For Option A, name the setting, describe in words the program that would split the messages and tally the words, and say whether and under what limits the group should run it; for Option B, name the kind of text, say whether the program should normalize it with strip and lower or keep it exactly as typed, and explain why.
- Use at least two of this week's terms (string method, split, normalize, whitespace, count) correctly.
- State the strongest case for a view you do not hold, in one or two sentences.
- Never quote real messages written by other people; describe them in your own words.
- Length: roughly 150–250 words if written. You may instead record your post as audio or video (about two minutes) and attach a transcript; both forms are scored by the same rubric.
Your replies — by the second due date (the end of the module week):
- Reply substantively to at least two classmates.
- A substantive reply does more than agree: run a two-line normalize program on an example from their post and report what it hands back, name someone their position could leave out, or make the strongest fair case for the side they did not take. "Nice point!" on its own does not count.
What a strong post looks like:
I chose Option B. A campus event form asks whether you will attend, and I think it should normalize that reply with strip and then lower, because "Yes", "yes", and " yes" all mean the same thing and a program that misses one leaves someone off the list. The same form also asks for a preferred name, and I would keep that exactly as typed, because a capital letter in a name is part of the name. Someone could argue that normalizing everything keeps the data consistent and easier to search, and that is fair, but I would normalize only the reply and store the name as given.
Notice how it names the kind of text, describes what the program does with string methods, takes a position with a reason, names who could be left out, and states a fair case for the other side. That is the bar.
Participation rubric
This discussion is worth 10 points. The three criteria below look at your initial post and your peer replies.
| Criterion | Full credit | Partial credit | No credit |
|---|---|---|---|
| Quality of the initial post (4 pts) | A specific setting or kind of text, a description of what the program does with it, a clear position with a reason, and a fair statement of another view | A setting is present, but the program stays vague, or the position is asserted without a reason | Missing, off-topic, or no reasoning about running string methods over people's text |
| Use of course concepts (3 pts) | Uses string method, split, normalize, whitespace, and count precisely, with every claim about what a method hands back matching a run | Uses a term loosely, or says a method changes the original string | No course terms, or used incorrectly |
| Engagement with peers (3 pts) | Two or more substantive replies that extend or challenge a classmate's reasoning | One substantive reply, or replies that only agree | No replies, or "I agree" with nothing added |
Post early if you can — the best threads happen when people have time to reply before the second due date.
Built with The Course Maker · samples.thecoursemaker.com