[wiz21]

> They aren't called patterns, they are called techniques.

I totally agree. That's weird to see the n+1-th geek discovering something people have been doing since the dawn of humanity.

Damn, we're just talking about basic cooking. I understand many of us didn't learn the basics, but nonetheless, it's basic.

Imagine somebody saying he discovered "patterns to ride a bicycle" and explaining how to go from A to B with a regular bike in the most obvious fashion...

[mercer]

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?

[VLM]

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)"

[batbomb]

Because there is a common vocabulary you lose when you do that, and it makes it harder to communicate without it.

[appplemac]

Patterns to ride a bicycle? Sounds interesting…