top of page
Search

Week One Wrap (or maybe roll?)

  • Janie Warren
  • Jan 18, 2022
  • 2 min read

Jiro Ono, Master Sushi Chef
Jiro Ono, Master Sushi Chef

Imagine doing something for 70+ years, receiving the most prestigious international awards for what you do, and having people come from all corners of the earth to experience what you do, and still thinking "Nah, I can do better." Jiro Ono, the almost 100 year old master sushi chef, feels this way about his craft.


We spent our first week getting familiar with the idea of craftsmanship, its history, and its relevance today. Jiro Ono's story was included in week one's module and we got to watch Jiro Dreams of Sushi. This man is fascinating, I've never seen anything like him!


There were many takeaways from the documentary and the other resources on the topic of craftsmanship, but I'll just share my top three:

  • Shokunin is a way of life. There is no direct english translation for this Japanese concept, but it sums up the key characteristics of true craftsmanship. It's the idea of truly and completely loving your work or trade, so much that it becomes everything that makes you, you. It's finding joy in the pursuit of perfection for your work, with an understanding and appreciation of the fact that you will never achieve it. And it's the dedication to working as hard as you can, every day that you can (even... no especially on the days you're not feeling that love or joy), because you know that's what it takes.

  • Maybe perfectionism isn't that bad. One of the lesson's resource article's author, Ria Tagulinao, had this to say:

Perhaps the strongest case for the shokunin’s unforgiving perfectionist instinct is that it inoculates him from the real enemies: mediocrity, complacency, and stagnation. He may not improve by leaps and bounds, but he is never not improving.
  • A good craftsman knows how to ask good technical questions. I do believe there are no stupid questions, but I do think there are poorly thought out questions. We learned a few tips from the mentors to help us ask better technical questions:

    1. Read the error.

    2. Clearly identify and document the desired outcome.

    3. Ask Google first.

    4. Read the error again.

    5. Summarize and document what methods have already been tried.

    6. Then ask a mentor or peer.

I enjoyed the first week's learning module. It helped put things into perspective. Looking forward to week two!

 
 
 

Comments


bottom of page