Very precious informations in this video, thanks

This is gold!!! Congratulations on the video.

Pandey ji ka beta hu chumma chipake leta hu . kzbin.info/www/bejne/aYC5c3eYfpdjgpo

10:26 😭😭😭

Key Points: 1. Success in the world of software engineering is a not an overnight process. You need to be patient. 2. Learn to code by doing projects. Following tutorials will only get you so far, you need to get creative, code projects, fail and relearn iteratively. 3. Writing good code, comes after learning to code. You start improving on code quality by getting feedback or by reviewing others' feedback. 4. Debugging is always relevant. Features may not make it to production but their will always be a need to resolve issues or improve existing code. Debugging effectively will help you save the team when things don't go as expected. 5. College != skills, it gives you a network you can tap into, for interviews, projects etc. College doesn't quite prepare you for the actual job. One of the reasons is the model of failing for an incorrect answer, this goes against process of learning to code. 6. Imposter Syndrome, happens to everyone don't it bring you down. Reframe it as an opportunity to learn, or have an honest conversation with a senior dev.

never listen to this youtubers they are full of crap in them

🔥🔥🔥💯🥂🥂

I've been trying to become a better mentor since I feel like it is an essential skill as I gain more seniority.

The #1 tip in this video is to graduate in 2009

I'm an Accountant by trade and I'm self taught in Python, SQL, and C++. I have to say, these additional skills have increased my earning potential immensely. One thing I've struggled with is balance but I've got it down now. I know the grind grind grind advice is so prevalent in our lives today. However, I wanted to remind everyone that taking time to rest, recover, spend time with loved ones, etc. is so incredibly important.

My lack of self-advocacy really came back to bite me in the rear end. I was at a startup and it was super fast paced and fun to work at. Contributed 43500 lines of code over multiple repos in 12 months. There was no style guide, and had a couple of PRs(exactly 2 PRs) that a more senior dev had comments on (some valid, and some completely seemed like they were trying to block me from shipping a feature) Got PIPed out nowhere, and have to look out for jobs now lol. I am not even able to feel bad. My mistake? -I should have documented all of my shipped features, and leveraged the code contributions in one on ones. - The minute the first PR went sideways with unnecessary nits, I should have written up a style guide doc and circulated it among the other engineers

How can these careers that suppose to have a high future employment growth are so difficult to get a job initially...!!!???

Homie yappin about bs

Me: Wow, this video seems very helpful 10 seconds into the video Rahul: Stanford computer science student Me: Nvm

I'm your biggest fan:)

Thanks for such great advice! As a first-year CS student, I feel that all the tips you have given in the video are very useful and will help me throughout my career.

Thanks for help know basics of kotlin

Awsome videos @Rahul Bhai !

Amazing Thank you

I failed so many times before landing my first software dev position. But eventually I learned how to answer the questions I was once unable to answer

This is bit wrong about books. Yes books won't magically make you a coder but you won't get very far without getting into the depths of books. Question is which chapter to read. Straight to keyboard is shallow you do have to make it work for you. Yes you need to work on the chair

Hey, man, you look really young and fresh despite 15 years of engineering, how is so? :)

Why was this video not uploaded 4 years ago 😭?

Amazing insightss, thank you so much rahul!!

Could get a holistic view of how to become a very good engineer. Thanks Rahul for sharing your thoughts.

Thx for your video.

I am not a software engineer but I work in IT so I can relate to most of what has been said in this captivating talk ! Thank you for your valuable input

Becoming a developer when ChatGPT can spit out code is too late if you are a student.

The question now is how deep my knowledge of DSA should be.

Some Points that i have noted 1. Learn code by doing(build project, avoid tutorial hell) 2. Debugging is important very important 3. Your network is your net worth (focus on giving more rather than taking) 4. Imposter Syndrome (Learn from professional those who know better than you in the specific domain) 5. Finding a job (study a lot care a little for interview) allocate some time for applying job with a consistent schedule. 6. Writing a Good Resume. avoid overloading format should highlight professional skills avoid summary section use generic format 7. DSA is Valuable for interviews 8. Behavior Interview are very important 9. System Design Interview (making assumption on how to design a solution to a problem. 10. How to succeed in Job? Get feedback and work to improve it. Accept feedback as much as you can. ask-> What can i do better than this. 11. The secret of Growing fast Be Deliberate Understand what is important to you. 12. your manager is really important

*One golden nugget* I would give you from my personal experience so you don't make the same mistake I made is don't be so focused on honing your technical skills that you ignore social skills. You would be working with human beings and in environments ranging from worst case scenario (Surrounded by psychopaths, sociopaths & narcissists in a cut-throat toxic work culture) to best case scenario (Surrounded by leaders patient, collaborative and reasonable people in a supportive work culture). Prepare for the worst and hope for the best and remember all that works for you in a supportive work environment would work against you in a toxic one. For instance .... 1. Being vulnerable and admitting you don't know might be encouraged in a supportive environment but you will be torn apart and be harrassed in a toxic one because everyone expects you to be Einstein. More reason why most of your team leads you will work with will have a God Complex. 2. While being shy and nervous during presentations, people might encourage you and be patient until you get your standing in a supportive environment. You would be mocked, harassed and humiliated in a toxic one. 3. Being open and bonding with your colleagues might lead to high-quality work in a supportive environment but would work against you in a toxic work culture... You don't want to know what people are capable of doing to each other to survive. (Mental Health Issues is a real thing in the tech industry and in extreme cases people commit suicide so protect yourself by all means necessary) So prioritize understanding the environment you find yourself in and the people you are surrounded by before being open or vulnerable or you might just learn the hard way like your predecessors. I hope it helps

Thank you very much for this! I learned so much.

Finally a video by an industry professional and not some kid who only makes YT videos! This is great advice, thank you for sharing.

how do you look like fresher still

This is genuinely incredible. Thank you for taking the time to make this !

You could tell the job market has become so bad that these tech influencers are not getting views on their videos. Just doing leetcode not gonna get you a job now since everyone is doing and getting better at leetcode.

Noice❤

you studied in Standford brother I studied in India and not so famous university learned from staffs who don't even know to teach that great what to do I have no mentor I should help myself

If you're typing along or need time to process this info (like me) try changing speed to .25 and as a free bonus you can hear Rahul explain this while super-drunk.

Disliking due toh thumbnail. You feeling like shit, head to the toilet, dont put it on camera

I contracted there. You literally cannot pay me to go back.

Thank you for this Rahul!

15 years in the business and ended up selling courses on YT? I'm getting TechLead vibes.

I wish I saw this when I started coding, back in 2013 as an ex Amazon he’s spot on

😂😂😂 matlab kuch bhi.

A 1337 engineer has terrible hand writing ;)

that tilted outlet on the bottom left is killing me lol

I've just subscribed to you and would definitely share it with others as well. Its been an year since I started in my software engineering career and this video is a great start for me to begin things with. Even though its an year, I still feel like I am navigating in a sea still figuring out what to learn as still there's a lot to learn. So For Example, There are so many things which I feel to Learn like LLD, Design Patterns, or AWS etc. Can you tell me one thing like I feel there's a lot to learn and see there are many things on my plate and I fear I might take a lot of time to learn all of this. How would I tackle this situation ? Iam very thankful if you can advice me on this!!

Solid gold. Thank you Rahul.