Hacker News Reader

Comment by pydry | Hacker News Reader

>In cooking, you usually know the recipe and have experience before preparing it for many people. In programming, you often explore and create, trying out new things that you didn't know before.

Im pretty sure that experimentation equally well to cooking.

View on HN

There is experimentation in cooking, but not usually in restaurants while serving actual customers. That is the time for just making the recipes you practiced.

There is very little reason to write out (say) the same algorithm a hundred times because you have a hundred different users who need it, but a cook can't just ctrl-C ctrl-V a dish.

I think that's the case for for lower-end restaurants, but for high-end restaurants, they are going to be tweaking things as they go. Ingredients are never perfectly interchangeable because they have to be grown or raised in real-world conditions that vary from one farm to the next or one season to the next.

Is this something that you know from actual restaurant cooking experience? Because high end restaurants lean extremely heavily on the concept of practice sessions where the cooks practice individual dishes over and over and perfect the mise en place for a specific menu ahead of time. Especially high end restaurants go out of their way to make sure that any experimentation will have been done ahead of time and not discovered at showtime.

High end restaurants measure everything both quantities, time and temperature extremely precisely and have strict quality control for the ingredients they use in order to ensure a consistent experience.

Sure, but the ratio is way different. I frequently cook the exact recipe the exact same way as I've done before, but I'd struggle to think of a reason to rewrite the exact same implementation of the same program.

Reply on news.ycombinator.com