Some key points from this video: 0:56 Trait 1: Be a feedback sponge - Treat feedback as a gift and proactively take action based on feedback. - Step 1: Write down the feedback - Step 2: Address the concern quickly. - Step 3: Follow up with the feedback-giver. 2:45 Trait 2: Obsess over time management and focus - Pareto principle: for many outcomes, 80% of results come from 20% of causes - Failure 1: fake productivity (feeling productive doesn't mean you're being productive) - Failure 2: poor productivity due to inefficient tooling - Machine time is cheaper than engineering time - How to be productive at meetings: - re-focus the meeting - add new information - offer strong opinions 6:10 Trait 3: communicate clearly (written and verbal) - software engineering ≠ programming - programming = talking to computers - software engineering = talking to computers AND people Thank you, Rahul, yet again for another informative video! 🙌
This is great, I have seen many smart software engineers who seriously lack these basics, but some average engineers who have built these fundamentals and have accelerated their growth and have become 10x engineers.
Great advice! Another trait of high performers is the ability to negotiate with stakeholders. Preventing scope creep is critical for the success of a project. BTW, the echo in the room is distracting at times. I recommend sound treating it by putting some foam on the walls.
Thanks for the video! My note would be (if you work from home) to schedule your work day around your brain’s optimal focus time. I tend to notice I am much more able to get into the zone in the evenings, so I do frontload my necessary “busywork” in the morning and clear my schedule for deep world later. HOWEVER: this can be a trap. If you do this, you must be very disciplined not to get caught in wasting time. Schedule meetings, unblock tasks and have a hard stop where you start deep work (for me it’s after an early lunch).
great advice! we touch on it a bit here in Taro: www.jointaro.com/lesson/JKmnr6rqBErUJMaeZLZ9/the-best-gift-you-can-give-yourself-when-it-comes-to-productivity/
I believe making a summary of rebuttal for each of the feedback would be an interesting aspect as well. It may help anytime someone going back to the feedback doc.
Urgency should be framed as the mindset for everything. Say no to things that are not impactful to your career so that you can say yes to the things that are. That will leave space to quickly reply to requests and impress stakeholders who will leave you positive peer feedback. Urgency doesn't mean you stay up all weekend cramming to get something done, but it does mean you can tell someone in a day or less how long and how much effort it will take to get it done. That way the person can ask that something be done with less effort if it's important, or align schedules to make sure they know when to expect it from you.
Being a feedback sponge is the right reaction to constructive, timely feedback. But what should you do when you're given negative feedback too late to do anything about, and then not promoted for not knowing hidden expectations? Basically how can you tell when you're not being adequately supported by your manager vs. not reacting well to feedback and should improve your own absorption?
Negative feedback (especially in a performance review) should never be a surprise. I'd recommend having "awkward" conversations with the manager to ensure you're discussing expectations regularly.
I have often seen that, even on smaller companies. One person finds a solution / optimization and they just kind of seem to assume it is obvious or whatever and do not say a word to anyone. I guess there might be many reasons. For one, it could be fear of other people getting mad at them for sharing what they did as the other person might not see value in it, or they feel it is really nothing and they feel they could be shamed for sharing "such a simple process" or... anyway, maybe it is a matter of team cohesion. Let's face it, it is a bit difficult to really trust your teammates when the company often makes it feel like a competition to "climb" and get that promotion and raise.
This is incredibly depressing. So many people have been enslaved to the matrix to care this much about their "careers", working hard right when you wake up just to make a billionaire richer. Couldn't be me. As an employee, I aim to work the least while still being paid the most. This is why I strive to find companies that I can work 10-20 hours a week while still keeping my job as a senior software engineer.
@@RahulPandeyrkp How can I get compounding value from a day job? The reason why you're doing RUclips vids is the exact reason why I will not spend most of my energy maximizing my career. There are other ways to make myself richer than pouring my soul into a "career" which is just matrix enslavement and synonymous to "let's make a billionaire richer"
There is some valuable information here BUT there is an awful lot that is purely subjective, and varies from one person to another. What is good for Rahul is not necessarily a good for you, the reader of this comment. It's not a one size fits all. If someone prefers to check their email, instead of coding, before their daily stand-up, there is nothing wrong with that. What matters is that developers are given flow time...that is large bands of time without interruption or meetings, allowing them to get into the flow.
Product Hunt launch: www.producthunt.com/posts/taro-tech-career-mentorship
Some key points from this video:
0:56
Trait 1: Be a feedback sponge
- Treat feedback as a gift and proactively take action based on feedback.
- Step 1: Write down the feedback
- Step 2: Address the concern quickly.
- Step 3: Follow up with the feedback-giver.
2:45
Trait 2: Obsess over time management and focus
- Pareto principle: for many outcomes, 80% of results come from 20% of causes
- Failure 1: fake productivity (feeling productive doesn't mean you're being productive)
- Failure 2: poor productivity due to inefficient tooling
- Machine time is cheaper than engineering time
- How to be productive at meetings:
- re-focus the meeting
- add new information
- offer strong opinions
6:10
Trait 3: communicate clearly (written and verbal)
- software engineering ≠ programming
- programming = talking to computers
- software engineering = talking to computers AND people
Thank you, Rahul, yet again for another informative video! 🙌
The behaviour, language, and working habits of those more senior to you and high performers, are such a great resource.
So much to learn from people around us!
I like your differentiation between a programmer and a software engineer!
Thanks!! I didn't realize there was a difference when I started learning how to code
This is great, I have seen many smart software engineers who seriously lack these basics, but some average engineers who have built these fundamentals and have accelerated their growth and have become 10x engineers.
Quickly becoming one of my favorite channels 🙂
Great advice! Another trait of high performers is the ability to negotiate with stakeholders. Preventing scope creep is critical for the success of a project.
BTW, the echo in the room is distracting at times. I recommend sound treating it by putting some foam on the walls.
Appreciate the feedback Jake
@@RahulPandeyrkp Rhode lav clip mic will solve it easily, $70
This is a very well done video and it earned my subscription. It is easy to follow and the structure is very valuable.
thanks Reid!
Loved it! This is so valuable. I would even recommend Cal Newport's "Deep Work" as a "how to guide" to get more heads down focused work done.
love that book!!
This advice hit my soul. feel like I need to watch this daily
Thanks for the very informative video. 🎉
Thanks for the video! My note would be (if you work from home) to schedule your work day around your brain’s optimal focus time. I tend to notice I am much more able to get into the zone in the evenings, so I do frontload my necessary “busywork” in the morning and clear my schedule for deep world later. HOWEVER: this can be a trap. If you do this, you must be very disciplined not to get caught in wasting time. Schedule meetings, unblock tasks and have a hard stop where you start deep work (for me it’s after an early lunch).
Then I am able to work until around 7-8pm uninterrupted before heading to the gym.
great advice! we touch on it a bit here in Taro: www.jointaro.com/lesson/JKmnr6rqBErUJMaeZLZ9/the-best-gift-you-can-give-yourself-when-it-comes-to-productivity/
Thank you for sharing.
I believe making a summary of rebuttal for each of the feedback would be an interesting aspect as well. It may help anytime someone going back to the feedback doc.
Great video Rahul.
Urgency should be framed as the mindset for everything. Say no to things that are not impactful to your career so that you can say yes to the things that are. That will leave space to quickly reply to requests and impress stakeholders who will leave you positive peer feedback.
Urgency doesn't mean you stay up all weekend cramming to get something done, but it does mean you can tell someone in a day or less how long and how much effort it will take to get it done. That way the person can ask that something be done with less effort if it's important, or align schedules to make sure they know when to expect it from you.
The one I am most interested in is "Excellent Communicators"
Being a feedback sponge is the right reaction to constructive, timely feedback. But what should you do when you're given negative feedback too late to do anything about, and then not promoted for not knowing hidden expectations? Basically how can you tell when you're not being adequately supported by your manager vs. not reacting well to feedback and should improve your own absorption?
Negative feedback (especially in a performance review) should never be a surprise. I'd recommend having "awkward" conversations with the manager to ensure you're discussing expectations regularly.
ruclips.net/video/ADWkkJtZna4/видео.html
True words ⭐⭐⭐👏👏👏
Did that high performing eng socialize that CRON job to others so they could leverage?
I have often seen that, even on smaller companies. One person finds a solution / optimization and they just kind of seem to assume it is obvious or whatever and do not say a word to anyone. I guess there might be many reasons. For one, it could be fear of other people getting mad at them for sharing what they did as the other person might not see value in it, or they feel it is really nothing and they feel they could be shamed for sharing "such a simple process" or... anyway, maybe it is a matter of team cohesion. Let's face it, it is a bit difficult to really trust your teammates when the company often makes it feel like a competition to "climb" and get that promotion and raise.
This is incredibly depressing. So many people have been enslaved to the matrix to care this much about their "careers", working hard right when you wake up just to make a billionaire richer. Couldn't be me. As an employee, I aim to work the least while still being paid the most. This is why I strive to find companies that I can work 10-20 hours a week while still keeping my job as a senior software engineer.
isn't it better if you can get compounding value from your day job though?
@@RahulPandeyrkp How can I get compounding value from a day job? The reason why you're doing RUclips vids is the exact reason why I will not spend most of my energy maximizing my career. There are other ways to make myself richer than pouring my soul into a "career" which is just matrix enslavement and synonymous to "let's make a billionaire richer"
@benjamin go become the billionaire then
❤❤
There is some valuable information here BUT there is an awful lot that is purely subjective, and varies from one person to another. What is good for Rahul is not necessarily a good for you, the reader of this comment. It's not a one size fits all. If someone prefers to check their email, instead of coding, before their daily stand-up, there is nothing wrong with that. What matters is that developers are given flow time...that is large bands of time without interruption or meetings, allowing them to get into the flow.
💎💯✨
gold.