Discussion about this post

User's avatar
Andreas Wandelt's avatar

As someone who likes to cook, and who actually has learned to cook in his early teenage years, I tend to disagree on one particular aspect here: What, for you, is a recipe? It looks to me as if you use it as a synonym of "algorithm". And you've made that craft versus algorithm argument elsewhere and I agree with that. But what does a recipe contain? It asks for an egg, but you need to scale it up by 1.5. What do you do? It asks for this spice but you have only that. It doesn't ask for certain vegetable, but you add it in anyway because if you leave it one more day until tomorrow, it will not be good anymore. And then it tastes great, actually, and you add it to your personal copy of the recipe, which you keep in your personal cookbook.

There is a lot of craft in applying recipes!

That is different from the craft in implementing algorithms. An algorithm is a fixed thing mathematically defined. You can make implementation errors or shortcuts or there may be efficient or less efficient implementations. But the algorithm does not leave any room.

The recipe does. "Season to taste!"

-------

[addition after publication] Upon further thinking, I think I need to add to that. I see a recipe as what you have called a heuristic. What was asked from Andreano was to algorithmify the heuristics expressed in his recipe. By giving the words of it, with all the open ends and the need for case-by-case judgement that has to be applied to "implement" it, to a company who would (need to!) turn it into a repeatable algorithm, he would have given maybe his name, or at least something of himself, and would have allowed it to be turned into something entirely different.

So, IMHO, A recipe is absolutely ok to use, because it is only an orientation, a guidance. Alchemists used recipes all the time ;-)

No posts

Ready for more?