solid advice, the same advice my tech lead gave me, but I somehow forgot about it. your video popped up and reminded me again. thank you!
That is good advice, on how to climb the corporate ladder, in a mega corporation. I've been at this for more than forty years. And I've seen a lot of managers with just a few years of coding experience get promoted beyond their skill sets, resulting in high turnover and then layoffs. They don't last. While you are solving those problems, you should continue to study, and work to analyze the code that the other engineers have written. in other words, you should be focusing on self improvement. If you're focusing on corporate advancement, that is what you will become skilled at, it will be obvious to everyone, and you may look good to your bosses, but your colleagues will be talking behind your back. Eventually it will be obvious to everyone that this is your primary skill, and that you don't add value. Then your entire team gets laid off with you.
Helping others is not just transactional. Mentoring others and celebrating their wins is not just about visibility. It is about building trust into the culture of your team. Getting code to work is just a part of the equation. Yea you hit a home run today, but your team could still lose. I hope you don't burn yourself out chasing visibility. I hope you drive meaningful change. That's where you'd learn best and contribute the most
i'd say a lot of these points are short sighted they may work for a while, but eventually, you will be figured by your colleagues that arent chasing visibility above all else friendly warning - the latest tech purges were extremely brutal towards engineers that seem to follow this trend, and managers that hold part of the blame for enabling such behavior my suggestion (15 years in tech) is to play the long game and just do good engineering, instead of spending too much time thinking how to look good some work isnt visible, nor does it show immediate impact, but it may be way more important in a grand scheme - and good engineers, or bosses (the ones that really matter) will respect that
I’ve seen and worked with too many fakers, like “managers” who don’t know how to do or cover any work, people who claim the project without the knowledge on how to do it (and just steal others’ credit once they get them done on their own). Stay away from the fakers and don’t become one.
Loving these consistent uploads!
Sick advice. The more I am in my engineering career, the more I learn how rare people are who actually enjoy writing documentation. As I venture into management, I’ve been trying to build up more documentation culture with my team but have been having trouble selling it to them. I’m going to bring these points to them as well as share your video.
Great content Alex, keep up the great work man ❤
Thanks!
Great video! Thank you for sharing, liked & subscribed!
I really liked this video. Why you should help others, how you get visibility, why you should toot your own horn, etc.
Thank you so much, please, keep these videos coming up. I'm learning a lot
Thank you for the video🙏... COMMUNICATION is sooo important yet so hard. Most of my work stress comes from me knowing something I think that no one else knows.
It's not that we don't touch codes, it's that we have more important to handle, for example watching YouTube or surfing, or eating snacks
I have been learning to ask for help after a 30 minute timer… it hurts the ego sometimes, sometimes I feel like I should be better… but this actually sounds like sound advice thank you
That's the corporate politics, I prefer to rely on my practical skills, don't care about making myself visible in the corporation, thus anytime when they fire me I can easily find job on free market.
10 year in engineering. I've only seen rockstar coders be promoted to high positions in companies, as in their code changes changes the industry, which is rare I can count on my hands how many people did it this way, the other way which he describes is the most common way to be promoted.
1 thing to add - if you are in a terminal role, you might simply like it there; Unless the pay difference is significant, you might want to evaluate if you want to move to a less coding oriented role.
You're on track to be the expert. 🎉
@FredChallenges