Skip to main content

Haute Cuisine, Fine Dining, Steaks, Dumplings, Quality and Other Matters


Today had an intense conversation at lunch regarding the food. No, The Food.

Discussion evolved around experience with very expensive restaurants that use some famous brand names, but the food is not so good.

Some people say it is "experience" that people pay money for. Then the experience should make food better for money.

As an example there were some stories: 4 (four) dumplings for $60 that were made in front of you, $45 stake which is shit, $600 bill for 5 (five) people dinner after which they went to nearest McDonalds to eat, because they were still hungry.

There is an opinion that it's better to cook for yourself - get the best meat (if we are talking about stake) from the shop, get the grill - there you go. But then some people say that then maybe chefs will do IT too? This supposed to mean that IT skills are the same as cooking skills. Quite possibly if the cooking skills were not just something basic that everybody can do. But then again there are people who doesn't think so. For them cooking is something extraordinary.

Who are chefs? Project managers or creators?
Project managers in many cases don't have an idea of the project. That means they didn't create it, but rather execute it using some tools. Chefs or even the master chefs should be also creators. They should invent some dishes and then direct the team of other chefs to implement what they envision.
There is also a prejudice that you can't buy wagyu or other type of steak of fine quality in a local shop? What is the "fine quality"? Freshness, taste? What is it?

For those who think it is impossible to buy wagyu beef in retail (in Australia) here are some links to consider:



To be continued...

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like...

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi...