Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FN1 updates #513

Open
AbbyANoble opened this issue Dec 19, 2024 Discussed in #308 · 0 comments
Open

FN1 updates #513

AbbyANoble opened this issue Dec 19, 2024 Discussed in #308 · 0 comments
Assignees

Comments

@AbbyANoble
Copy link
Contributor

Discussed in #308

Originally posted by AbbyANoble September 11, 2024
Activity 2.1.4 - 2.1.6 go together and my students did well with them, especially in realizing that it might not be necessary to write things twice. I would recommend one additional exercise to go with this group though. 2.1.4 is one-to-one, 2.1.5 is not a function and also has repeated y values, and 2.1.6 is function but just isn't one-to-one. It might be good to throw in another non-function but no repeated y values. To help point out that it's because of the x-values having two different outputs.

I'd also recommend something to motivate why we care that an input has two outputs but not that the same output happened to come from two different inputs. I like to do this with a restaurant menu. Show them two potential menus and ask which one makes more sense or doesn't have any discrepancies if you were trying to order. Something like:

Menu A

  • Nuggets $2
  • Burger $4
  • Fries $2
  • Nachos $5

Menu B

  • Nuggets $2
  • Burger $4
  • Fries $3
  • Nuggets $5

So the first one is a fine menu. We can accept that two different foods have the same price. But the second is a problem. How much do nuggets cost? Who knows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant