Superb article. I think giving tech talks to your team/org is underrated. There have been cases where I refer to a tech talk months after it was given because it became relevant to me later on, which is a huge win for the maker of the talk.
Documenting processes and explanation of data systems on tools such as 'Confluence' have been useful for me at work. It reinforces my knowledge and helps me articulate complex systems to other stakeholders...
Thank you for another thought-provoking newsletter, Ryan! The concept of scaling oneself is crucial, and your practical strategies, especially on knowledge sharing and building tooling, are gems for engineers at all levels. Looking forward to more insightful content!
Just recently I started recording the onboarding presentations that I'm doing, so that they can be used later on to speed up the process. Next to that, since i'm transitioning into a mid-level / senior role, i'm also trying to spend more time documenting thought processes and design decisions to help the learning of our junior members
Excellent tips Ryan, especially about building tooling and improving the docs, those can essentially "replace" you and serve others when you're not present. Although, working in small startups all my life, never anyone told me "scale yourself" but "we should clone you". 😃
My boss called this, “Being a force multiplier”. If the whole team produces more when you are on it you are a force multiplier. Great post!
Superb article. I think giving tech talks to your team/org is underrated. There have been cases where I refer to a tech talk months after it was given because it became relevant to me later on, which is a huge win for the maker of the talk.
Documenting processes and explanation of data systems on tools such as 'Confluence' have been useful for me at work. It reinforces my knowledge and helps me articulate complex systems to other stakeholders...
My ex-boss used to tell me that my individual performance was less important than the collective performance of the team
Thank you for another thought-provoking newsletter, Ryan! The concept of scaling oneself is crucial, and your practical strategies, especially on knowledge sharing and building tooling, are gems for engineers at all levels. Looking forward to more insightful content!
Scaling yourself is the only way you can grow yourself (and others). The only sustainable strategy. I have written something similar here - https://open.substack.com/pub/buildtechcareer/p/how-helping-others-skyrockets-your?r=6lkk8&utm_campaign=post&utm_medium=web
You are absolutely right
There are some great tips in here, thank you!
Just recently I started recording the onboarding presentations that I'm doing, so that they can be used later on to speed up the process. Next to that, since i'm transitioning into a mid-level / senior role, i'm also trying to spend more time documenting thought processes and design decisions to help the learning of our junior members
Excellent tips Ryan, especially about building tooling and improving the docs, those can essentially "replace" you and serve others when you're not present. Although, working in small startups all my life, never anyone told me "scale yourself" but "we should clone you". 😃
Do you think that platform teams often have better chances with third option because thats their day to day job.