I think it's great that someone is trying to make cooking more approachable by using 'geek jargon'. Who cares that it's slapping a different label on an old thing?
Confusion when you meet a chef and try to learn something or at least commiserate about cooking and what he calls a béchamel you try to provide ... a functional programing lambda statement based on map and reduce statements applied to lecithin proteins using heat as an anonymous lambda function. Sorta.
Fooling around as a mental exercise is fun. Hey look at this, a floating point multiplier in BF! The problem is mis categorizing or mis titleing it as "learning floating point math". Describe Ops activity as a "insights from looking at cooking thru a programming lens" would sell a lot smoother than learn to cook using c++ design patterns.
There is a minor area of danger in that there are many ways to hurt yourself cooking but working slowly with common sense should prevent serious accidents (I hope?) Perhaps a good analogy to "don't write your own crypto" would be "don't invent your own canning recipes" or "don't invent your own deep fat frying procedures (unless you like burn wards)"
Fooling around as a mental exercise is fun. Hey look at this, a floating point multiplier in BF! The problem is mis categorizing or mis titleing it as "learning floating point math". Describe Ops activity as a "insights from looking at cooking thru a programming lens" would sell a lot smoother than learn to cook using c++ design patterns.
There is a minor area of danger in that there are many ways to hurt yourself cooking but working slowly with common sense should prevent serious accidents (I hope?) Perhaps a good analogy to "don't write your own crypto" would be "don't invent your own canning recipes" or "don't invent your own deep fat frying procedures (unless you like burn wards)"