Culinary Inspirations: A Developer's Reflection After Watching "The Bear" and Collaborating with Ex-Chef Friends
Tags: management, development, career
Published: 2024-01-17 00:33:01

Last year (2023), I watched some outstanding series—ranging from sports dramas (HBO's cancellation of Winning Time still pinches my heart) to the spectacular adaptation of the video game The Last of Us and obviously Succession. However, one series that lingered with me, especially after its fantastic first season, was The Bear (and was awarded a bunch of prizes this week at the Emmys).

In essence, _The Bear_ revolves around a kitchen and the human dynamics within it. At the story's onset, Chef Carmem Berzatto, previously associated with the world's most stunning restaurant, inherits an old restaurant from his recently deceased brother. 

He begins implementing innovative ideas he had gathered from his previous job. However, the team remains entrenched in the existing methods (the established 'system') they've been accustomed to. Upon rewatching the first and second seasons with my girlfriend, I realized there are several beneficial patterns and behaviours we could apply within our development and team environment. Here, I'll summarize these behaviours:

**Mise-en-place:**

Those who've worked with me know my affinity for this concept (mainly in the presentations) —planning and executing the basics before diving into the main work. It's about setting the right environment, planning ahead before presentations or hours of coding, and avoiding interruptions like fetching missing elements. The mantra is simple: Plan before work and ensure you're equipped to work properly. For musicians, it could be related to setting the tempo and tuning your instrument.

**Family Meal:**

Another fundamental concept for fostering a positive environment is the 'family meal', this concept was introduced to me by my dear friend and ex-culinary chef Fernando Toda. It's a time for the team to come together before (or after) work. The term 'family' signifies acknowledging individualities while emphasizing the need to work cohesively towards a shared goal. Work is often challenging, but you need your team, and they need you. Creating moments to bring everyone closer is essential.

**Consistency in Repetition:**

Like in a restaurant kitchen where you serve specific dishes repeatedly, coding often involves repetitive tasks, you always need to do some fetching, parse different formats and organize your data before using them. While you continuously improve and learn new techniques, consistency is crucial for delivering your best every time.

**Communication and Coordination:**

Some might disagree, but it's important to communicate effectively while also taking the time to listen and execute your responsibilities. Usually, the developers tend to do overengeniring and the same portion complains about infinities meetings. In the culinary world, responding with "OK," "OK Chef" signifies understanding and commitment. This work demands flow and pace—avoid lingering over things you're unsure about; prepare properly and be efficient.

**Craft with Love and Aesthetics:**

Do you genuinely love what you do? I'm not just talking about passion; I'm talking about delivering something that resonates with your heart. You can make a delicious cake but all the additional pieces which you can add make a difference, good presentation, and a stunning smell, these types of things improve the whole experience.

**Customer Focus:**

Pay close attention to your customers—immerse yourself in the experience of using your product, essentially becoming your own client. The concept of "dogfooding," as introduced during my time at Flaner, you need not just feed, you need to eat, and you need to delight with your product. Assume the responsibility as if it were for yourself.

**"Let it rip"**

In the kitchen, everyone has their designated responsibilities (like a sous chef, for instance). However, it's crucial to be prepared to step into the shoes of others on your team when needed. Likewise, you should feel assured that your team can handle your tasks when you require their assistance, recognizing that mistakes and learning opportunities are inherent in the collaborative process. Sometimes you just need _"let it rip"_, people will learn, ask, and think of a way to help you.



I wrote this article during a flight from Frankfurt to Lisbon, with all my reflections on the parallels between the tech/dev environment and kitchens. I was trying to spend some time, and I hope you find it interesting. Feel free to share your thoughts and comments here, let's try to do it collaboratively.



PT: Escrevi este artigo em inglês como forma de exercício, em breve irei traduzi-lo e postar aqui e no Linkedin.