Week 8 Discussion — Loud Slips, Quiet Slips — Traditional alternative (no AI)

Instructors: publish this instead of the adaptive version if you prefer, and unpublish or delete the adaptive one.

Hook

In Week 4 the line if x = 5: was refused before a single line ran, but in Week 6 a loop over range(1, 5) printed 1 2 3 4 with no error message at all, one number short of what its author meant. This week you gathered six classic slips into one checklist, and some of them shout while others stay quiet.

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: Some of the six classic slips stop a program loudly, such as a single equals sign in a condition, which Python refuses before anything runs. Others run quietly and print a wrong answer, such as a range whose stop was left out or two strings joined by a plus sign. Pick a program people would rely on, from your own life, major, or workplace, such as a dose calculator, a bus timetable, or a payroll sheet. Argue which kind of slip is more dangerous in that program, loud or quiet, and why. Use this week's ideas (the classic-bug checklist, a syntax error versus a runtime exception versus a logic error, and predict, then run) and say what someone who ranks the danger the other way would argue.

Option B: Some programmers read every program for slips and write a prediction before they ever run it; others run early and often and let the output and the error messages guide them. The second half of this course brings programs that hold whole lists of values. Argue which habit you will lean on there and when you would switch to the other one. Use this week's ideas (predict, then run; the classic-bug checklist; and reading an error from its last line) and say what someone who prefers the other habit would argue.

There is no single right answer. People who agree on every fact about what Python prints still disagree about which mistakes matter most and how to work, because those questions rest on judgment about the program and its users as well as on the facts. 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 program people rely on, name one loud slip and one quiet slip that could hit it, say what each would do when the program runs, and argue which is more dangerous there; for Option B, name the habit you will lean on and describe one moment when you would switch to the other.
• Use at least two of this week's terms (predict, then run; classic-bug checklist; syntax error; runtime exception; logic error) correctly.
• State the strongest case for a view you do not hold, in one or two sentences.
• 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 short program that shows the slip they named and report what it printed, name a slip from the checklist their example could also suffer, 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 A. In a shop's till program, a quiet slip worries me more. If two prices arrive as text and the program runs print("12" + "8"), it prints 128 and nobody sees an error, while a single equals sign in an if line stops the program before it opens, so somebody notices at once. Someone could argue a loud slip is worse because the till goes down mid-shift, and that is fair, but a stopped till is noticed in minutes, while a wrong total can go unnoticed for weeks.

Notice how it names a specific program, names one loud slip and one quiet slip, says what the quiet one prints, takes a position, 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.

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