←back to thread

359 points FromTheArchives | 1 comments | | HN request time: 0.238s | source
Show context
Imnimo ◴[] No.45293673[source]
I looked at the example for computer science basics for a 7th grader interested in food. Explanations include:

"a list can be used for a recipe"

"a set can be used to list all the unique ingredients you need to buy for a week's meals"

"a map can be used for a cookbook"

"a priority queue can be used to manage orders in a busy restaurant kitchen"

"a food-pairing graph can show which ingredients taste good together"

Maybe I'm over-estimating the taste of 7th graders, but I feel like I would get sick of this really quickly.

replies(12): >>45293709 #>>45293849 #>>45294241 #>>45294326 #>>45295433 #>>45295632 #>>45295729 #>>45295945 #>>45296066 #>>45297739 #>>45300529 #>>45301902 #
raincole ◴[] No.45295729[source]
> "a list can be used for a recipe"

I don't even know what it means, tbh. I feel it's going to confuse the hell out of 7th graders.

replies(1): >>45295753 #
kccqzy ◴[] No.45295753[source]
How is that difficult to understand? A recipe is an ordered list of steps of what to do. So of course a list can be used for a recipe.

I personally prefer a serious text without bringing in unrelated concepts like food, but this is still understandable.

replies(5): >>45296311 #>>45296696 #>>45297063 #>>45297726 #>>45301823 #
1. raincole ◴[] No.45297726[source]
Uh, exactly. See how you describe the same concept:

> A recipe is an ordered list of steps of what to do

Understandable.

> a list can be used for a recipe

Not so much.

Moreover, a recipe usually at least consists of two parts, ingredients and steps.

"pierogi_recipe": { ingredients: Set<(Item, Quantity)>, steps: List<Step> }

So the analogy kinda muddies the waters.