Newsletter #24: Five valuable lessons for a new tech lead and more
This month's newsletter contains links to my best discoveries in February.
In this peculiar time, I can't help but draw attention to what's going on in Ukraine. This demonstrates how fragile the world's peace is and why we must do everything in our power to protect it. I encourage you to join the movement and do anything in your power to support all that are affected.
As always, you can read my top discoveries for the last month below. If you like this newsletter, please forward it to others who might be interested.
Last month, I wrote about five valuable lessons for a new tech lead in collaboration with folks at leaddev. In the post, I talked about tips and pitfalls for anyone transitioning from an IC to a tech leadership role. Whether you’re an individual contributor who is thinking (or in the process) of stepping into a tech leadership role, or a manager who is overseeing such transitions, this article is for you.
Knowing what can make you fail as an engineering manager is crucial to succeeding. This post is full of insights for anyone looking to climb the engineering manager ladder and achieve the same level of results and credibility that everyone is expecting, especially yourself.
One of the major shifts one can make about leading is getting out of the way and supporting your team from the back. This post talks about the biggest misconception of leadership. My best takeaways from this post are:
Enable your team to make the right decisions.
Leading your team is not about doing it all yourself.
Keep your team focused on what matters.
It’s normal for companies to hire new leaders when there are problems that need to be addressed. But what should you do when your team is struggling? This article presents two questions to ask when your team is struggling.
Ian Nowland, SVP Core Engineering at Datadog, offered a framework in this post that divides software engineering management into seven categories: engineering, execution, operations, people, product, partners, and company. I find this framework valuable. It has helped me look inward in my approach to leading software teams.
Notion is a well-known documentation platform. One of the interesting things about notion is its flexibility when it comes to re-arranging content and moving things around. Content of various types and structures can be created and moved around. This article sheds light on the data model behind the notion's flexibility.
In my previous newsletter, I discussed how to drive technical initiatives that span multiple teams. Driving and tackling technical challenges that span multiple technical teams and organizational systems is one of the ways to thrive on the technical leadership’s path. This post outlines a very senior engineer's strategic (and impactful) work.
I’m Hiring Tech Leads In Europe