What NOT to do as a new engineer: message everyone on the team "What did you get done this week?"

@youmemeyou

Жыл бұрын

J

that cold start algorithm is something I have never heard of anywhere else. top tier advice 🙌🏼

@RahulPandeyrkp

Жыл бұрын

credit to Boz for that :)

@sapnabl

Жыл бұрын

I agree, thanks

Yeah, the Cold Start Alg. is OP. I saw it in action from both sides: as a new joiner and a person already working on a team. Apart from getting you up to speed, it also establishes a connection between team members. It makes it easier psychologically to ask questions later and for other people to reach out to you. From myself, I would add - be generous and sincere with compliments. If somebody takes their time and shows you around the codebase, helps you with something, etc. Praise them during standup (or your communicator/kudos channel). I mean they've actually helped you, so it is not only a nice thing to do (they will be more eager to help you in the future), but also it gives them some leverage when talking with their manager about mentoring. It really builds the team and your manager will notice this too,

Joining a team for my first ever project so this video dropped at the perfect time! Thanks!

been binge watching your content. still can't believe this is all free. i'm learning so much. ty 👌

@RahulPandeyrkp

Жыл бұрын

thanks Eric!

Big thanks for the video since Im about to start a new job.

Never heard of the cold start algorithm - thanks for the advice! Peace and much love brother!

Thanks Rahul! This is incredible advice. The two bucket approach and cold start are something I wish I knew earlier in my career.

Came through to tell you your thumbnail is exceptional, sir! 👍🏾

Rip to the people who came into a company/internship with a non existent onboarding process. The one I am in did not have one and I wasn't given good tickets to work on so I learnt little in the first 2 months. I was given inconsistent bugs which is very difficult, especially as a intern. It's getting better now as I'm getting features to work on. In hindsight I should've asked for a feature early on. Next time I find an internship or job I will ask about their development processes to make sure they do things right new hire wise.

@RahulPandeyrkp

Жыл бұрын

Most companies unfortunately have a poor (or non-existent) onboarding process.

@CaliburPANDAs

Жыл бұрын

Can you elaborate on the bad tickets you were given? What would you ask them about the development process to ensure a better experience for new hires?

@skyhappy

Жыл бұрын

@@CaliburPANDAs The first ticket I was gotten was not carefully chosen by my manager, he just asked someone else to assign me something, and that guy also put little thought into it and gave me a inconsistent bug to work on. Solving inconsistent bugs requires much more of an understanding of the code base than consistent bugs. It's also frustrating because you may be unable to reproduce it which is the first step. I never want to work on an inconsistent bug again in my life. When you're asking questions to a potential employer I recommend asking them ospecifics of what their onboarding process is like. And other stuff like how their testing process is, what kind of tests they do, what frontend and backend testing frameworks, etc. Your goal is to figure out how organized they are in their processes. If they are disorganized they will probably have a nonexistent onboarding process among other things like no designers in your team (like mines lol so there are visual inconsistencies). Also try to figure out good the product team is. At my place they don't document things and have poor communication of the product roadmap and current project. Also, ask about their documentation practices. Poor documentation will mean they have poor knowledge transfer which is very important as a new hire.

@CaliburPANDAs

Жыл бұрын

@@skyhappy thanks for the tips 🤗

@skyhappy

Жыл бұрын

@@CaliburPANDAs yw

I needed to hear this

Nice to get a look inside these thought processes

@RahulPandeyrkp

Жыл бұрын

that's one of my goals with the channel and joinTaro! sharing the "insider" perspective

The thumbnail was lit! xD

Thanks Rahul

Honestly, these videos aren't software engineering videos but professional guidance videos. If I had some of this knowledge at the start of my mechanical engineering career, I could have avoided so many blunders

Thumbnail is 🔥 😂

Would like to see a video on how a software engineer working in Infrastructure org compares to a Software Engineer working in a Product org. Their works are slightly different. Product has more of APIs and using different tools. Infrastructure is more focused on distributed systems and scaling of their apps. They're the ones who make the tools, more focused on C++ rather than creating web apps (IMO). And how the career of both these Software Engineers differ.

Interesting 🤔

I think the transitions detract a bit from the content. Consider toning them down/going for something more elegant

@RahulPandeyrkp

Жыл бұрын

thanks for the feedback

Love the thumbnail😂

@RahulPandeyrkp

Жыл бұрын

haha credit to Alex, I know very little about anime

Hi Rahul, I wanted to ask you if I’m looking to be a software engineer, is it enough to only know the JavaScript programming language or do I have to also know Python?

@RahulPandeyrkp

Жыл бұрын

It's not enough to know a specific technology IMO. Instead you should focus on what is required to build impactful projects which actually do something meaningful. Most good companies won't care about how well you know a specific technology, they only want to know that you can build something interesting.

for the second bucket of people, could you elaborate on why a noob's pov might be useful to them? i could see how maybe a fresh perspective is useful, but if you're lacking a bunch of context then is it all that useful? or maybe I'm misunderstanding this point.

@RahulPandeyrkp

Жыл бұрын

Someone new will lack context in the new environment, but they hopefully have a good grasp of their old team/company. They could they offer a perspective on how the new environment is different, and what learnings may come from that. Alternatively, they could share their initial impressions from talking to others on the team and offer a perspective on priorities.

Is the native mobile dev role, a bad role considering the number of job opportunities in the market?

@RahulPandeyrkp

Жыл бұрын

I think native mobile dev is still great

Do you offer services for coaching for junior engineers ?

@RahulPandeyrkp

Жыл бұрын

that's what Taro is for: jointaro.com/membership

🙌

Now you are called Taro Pandey

@RahulPandeyrkp

Жыл бұрын

Need to find some alliteration

the video effects used at around 4:01 is wonky lol

@RahulPandeyrkp

Жыл бұрын

some 3d stuff going on

@vijal-patel

Жыл бұрын

@@RahulPandeyrkp It was a great video nonetheless

A newly hired engineer is not going to create their own onboarding doc. They also are very rarely going to be able to choose their own starter project. This video is for managers and team leads. Many of these tips are not really actionable for the people going through onboarding themselves.

@rdean150

Жыл бұрын

That Cold Start process sounds like a solid approach though. Need to remember that one.

The shoulders look weird lol.

@GrandTerr

Жыл бұрын

Added the video to watch later, thanks!

damn t shirt size is so non-intuitive

@RahulPandeyrkp

Жыл бұрын

What's confusing about it?

How embarrassing it must be to work for Meta.

😅 Pᵣₒmₒˢᵐ