adorn_percentages("col") (per our conversation today)

[rhinopotamus]

So you were totally right: I took a quick ctrl-f through all the modules, and you only ever adorn column percentages, so there's no inconsistency.

Okay, so then here is maybe a suggestion. What if there's a brief little thing when we first introduce adorn_percentages("col") that says, here we are interested in column percentages for such-and-such reasons, here's how we do that, bam, okay but what if we're for some other reason in some other table interested in the row percentages, okay well adorn_percentages("row"), bam".

Alternatively: what students are ever going to do wrong is they're just going to leave the specifier off and not notice. So maybe instead, a thing says "what happens if we accidentally leave off "col" in here? oh no, that's row percentages, compare what happens when we say "row", wow yeah those are less useful here."

The reason I'm putting this in as a "suggestion" rather than making a pull request is because (a) low bandwidth today lol and (b) I'm diffident about the pedagogical value of this move. Maybe it shows them a thing to watch out for, but maybe also it just muddies the waters.

[VectorPosse]

Good points, all. I'll hold onto it in the issues for the next round of edits and consider it then.

…

On Wed, Oct 5, 2022 at 4:41 PM rhinopotamus ***@***.***> wrote: So you were totally right: I took a quick ctrl-f through all the modules, and you only ever adorn column percentages, so there's no inconsistency. Okay, so then here is maybe a suggestion. What if there's a brief little thing when we first introduce adorn_percentages("col") that says, here we are interested in column percentages for such-and-such reasons, here's how we do that, bam, okay but what if we're for some other reason in some other table interested in the row percentages, okay well adorn_percentages("row"), bam". Alternatively: what students are ever going to do wrong is they're just going to leave the specifier off and not notice. So maybe instead, a thing says "what happens if we accidentally leave off "col" in here? oh no, that's row percentages, compare what happens when we say "row", wow yeah those are less useful here." The reason I'm putting this in as a "suggestion" rather than making a pull request is because (a) low bandwidth today lol and (b) I'm diffident about the pedagogical value of this move. Maybe it shows them a thing to watch out for, but maybe also it just muddies the waters. — Reply to this email directly, view it on GitHub <#51>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3M3H3JUK7QD27V6542HNTWBX7YFANCNFSM6AAAAAAQ57RIYE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>