• Home
  • Writing
  • Resume
  • Home
  • Writing
  • Resume

Writing

  • Why Some Managers Look Disingenuous

    January 3rd, 2024
  • Do’s and Don’ts For Technical Interviews

    December 27th, 2023
  • The Book That Made Me Want To Be A Leader

    October 30th, 2023
  • How to Fail An Interview As the Interviewer

    October 25th, 2023
  • Should Managers Be Prescriptive?

    October 16th, 2023
  • How To Help Unmotivated Developers

    July 12th, 2023
  • What to do when nothing seems good enough

    July 10th, 2023
  • Why Do We Burn Out?

    July 7th, 2023
  • What I Taught You, I Don’t Know

    June 21st, 2023
  • How To Delegate Effectively Without Feeling You Are Losing Control

    June 12th, 2023
  • Let’s Accept It. Technical Interviews Are Broken

    June 7th, 2023
  • Why Managers Need Empathy to Manage Low Performers

    May 31st, 2023
  • The Slow Decline of Highly Motivated Developers

    May 24th, 2023
  • Why Writing Explicit Code Matters

    May 18th, 2023
  • Why Is It So Difficult to Assess Expertise in an Interview?

    May 15th, 2023
  • The Real Value of a Senior Developer When it Comes to Dealing With Uncertainty

    May 11th, 2023
  • Why You Should Use Feature Flags to Deploy with Confidence

    April 28th, 2023
  • Over-Engineering Is Not (Just) a Technical Problem

    March 20th, 2023
  • The proactivity fallacy

    January 25th, 2023
  • Extending typescript intersection with optional properties

    January 18th, 2023
  • Setting up Google Tag Manager in a Nextjs application with a strict content security policy

    December 27th, 2022
  • How to build a scalable folder structure for a nextjs app

    December 11th, 2022
  • Why I have stopped writing comments

    December 6th, 2022
  • How to efficiently type nextjs page's props

    December 6th, 2022

What I Taught You, I Don’t Know

June 21st, 2023

When I started working as an Engineering Manager (EM) I had the assumption that to be a good EM I had to teach everything I knew to the developers I led, and to do that effectively, every moment had to be a teachable moment.

You may have felt the same or seen it in people who don’t want to let any interaction go wasted by not having a lightbulb moment.

That assumption put unbelievable pressure on my shoulders because every 1:1 had to be a crucial step in the developer’s career, every code review had to show a good insight on my part, and every conversation had to be insightful and productive. Suffice it to say I was not a very effective manager.

Over the years, after many hours of learning and much frustration, I started changing my expectations and thus changed how I approached working with my team. These are some of the hard lessons I learned

It takes time

Any serious learning takes trust and time. You can’t rush it. You can share your knowledge and your experience but you can’t really transfer it, the other person needs to take it in, assimilate it, accept it, internalize it, and ultimately live it. More, importantly, they need to be willing to do that.

And that won’t happen overnight. It definitely won’t at first when you and they are still getting to know each other. Be patient and allow the trust to grow organically.

I don't control everything

Years ago I read this quote, often attributed to Galileo Galilei

We cannot teach people anything; we can only help them discover it within themselves

It’s the first part that stuck with me: I cannot teach people anything. For me, it means that it is not about me, it’s about them. It’s not my job to make every moment a teachable moment. My job is to be there, share my experience, and ask questions.

When they are ready the learning will happen.

It’s not about teaching, it’s about learning

This is what I struggled the most in accepting about myself, although I see it quite clearly with some of the leaders I worked with in the past.

What I taught, I don’t know was once said to me by a leader I had in my early years of professional development when we were reminiscing about that time.

It took me a while to understand what he meant. It took me years, it took me to become a leader myself and experience it on my own to give meaning to what he said.

For me it means that you don’t need to do a conscious effort to teach someone something, I would even argue that if you do, you’re probably not helping. How do they learn from you if you are not “actively teaching”? They learn by looking at what you say and do, looking at how you connect ideas, and looking at how you help them realize the knowledge they had within them.

It is counterproductive

This seems like it must be wrong. Why would focusing on making sure each interaction teaches someone something and makes a difference in someone not be beneficial? Because it puts the focus in the wrong place.

When your goal becomes coming up with insights in every situation, you stop caring about whether those insights are actually helping the other person because the goal is no longer to help them but to keep the counter going. This is not necessarily something conscious and it doesn’t make you a bad manager or leader for doing that. It’s natural I think to confuse quantity for quality.

I will say though that what would make you a bad manager or leader is to not be aware of doing that. It is your responsibility to put the needs of people you lead always in front of your desires.

Closing thoughts

If you are a new EM and you think you need to be showing wisdom every time you say or do something, cut yourself some slack, and don’t be too hard on yourself. Expecting every moment to be a teachable moment will lead to failure and frustration, simply because it is not entirely up to you.