Sorry, I guess by definition this *is* a humble brag, but I still thought it was worth sharing. I mean, how else am I gonna remind you guys that I use to work at Google?
Crazy that a junior engineer was able to complete a legacy service migration with an independence. When I look back to my first job out of college, I didnt know what an API was, what a microservice was, what a monolith was, I didn't even know how to use GIT. None of those things are taught in school and leetcode didn't either.
@@tonghongchen4289Why though? I think the task is exactly right for a beginner because you've got the legacy service as a backup to keep along if things go wrong. So it isn't too bad in case the migration project goes to waste. Plus you basically have a working blueprint to copy the logic from. It's kind of a typical junior task tbh.
One thing I learned from working in tech: Reflection addiction Doing stuff gave me feedback, it was my job to interpret as much of that as I could, and reflect on it
not luck. You went out of your comfort zone, maintained composure in a stressful situation and you were proactive ( knowing ahead of time how to view the latency of the microservice ) opportunities fall upon everyone. Perhaps unequally but the point is to be prepared for when they arise.
Nice breakdown. I can tell about my Google experience: Joined as junior. Team is pretty competent but stuck running extremely fragile system in prod (fires everywhere, touching stuff is scary, infra keep getting deprecated forcing lot of migrations). First project is a manager's pet project that was never feasible, I have nothing to show after 6months. Manager quits after 9 months. I still don't have a project and now under a new manager, I'm stuck doing tedious cleanup that nobody wants to do for another 6 months. 16 months and I have nothing to put towards promo. Finally get assigned to a 2 person project with L6, but I'm able to contribute pretty much equally. 26 months in my Google career, the project is pretty much done (and good quality) but it's not launching because of politics. I still haven't launched anything and quit b/c I'm a little depressed and feel that promo is impossible.
Cool story! I was expecting that you'd be extinguishing all kinds of alerts and weird bugs for the following weeks, rolling back and rerolling infinite times. Neet job making it work from the first try!
Tbh, this is a typical junior project. You have a working legacy system as backup in case the migration goes to waste. Plus you have a working blueprint to copy stuff from. You basically just need to copy an existing service of the new tech stack and migrate the logic into it. A capable junior with potential should be able to dig into the problems and grow.
Good point. But if I can teach CS concepts to 10 people, maybe those 10 people will go on to solve those problems. I feel in this position I can be a positive multiplier.
My friend joined Tesla Energy as a SWE last year, switching from data analyst to SWE by following this channel. Totally agree with the positive multiples
Hey! I was plannning to make my own Load Balancer as a project. Could you provide me with some guidance. I'm Appplying for SDE-1 jobs and felt like this would be a nice project
If you think you are progressing with your task today compared to yesterday, then you're in a good position to explain why the task you're assigned to is taking time to the tech lead / manager. If not, there's no point in keeping it to yourself. Alert the team in the stand up meeting and try to resolve the issue with a mob programming session. Don't hesitate asking for help. Even seniors get stuck. Most companies encourage asking for help when you feel like you're stuck. I'm not sure if a company that discourages seeking help is a good company to stay. It's a sign to leave.
Any advice for someone whose degree taught them R, works as a database engineer using SQL Python and Java (Talend) for ETL, trying to get into full stack development/systems?
Sorry, I guess by definition this *is* a humble brag, but I still thought it was worth sharing.
I mean, how else am I gonna remind you guys that I use to work at Google?
true
It's fine. Most of the life story clips are gonna be humble brags, that's why we're here
Love it
Humble brag or not this was helpful. Working at Google and looking to get promoted this year
"I'M NEETCODE GODDAMMIT"
Mega chad
🦍
same thing I thought.
Rule 1. Never forget to mention Google
Rule 2. Never forget Rule 1
it works tho, channel was pretty unknown until google was mentioned
Yes,but he wasn't completely positive about it.
Smile fades away from junior to midlevel
babe wake up
it's a new neetcode story time
You’re really relatable, which is why I watch your videos. Right on
I really appreciate your honesty. Some people just completely ignore the luck factor. I believe in today’s it plays a huge part.
Crazy that a junior engineer was able to complete a legacy service migration with an independence. When I look back to my first job out of college, I didnt know what an API was, what a microservice was, what a monolith was, I didn't even know how to use GIT. None of those things are taught in school and leetcode didn't either.
Where are u from?
Which uni and how long ago
TBH that doesn’t sound right even for a junior
@@tonghongchen4289Why though? I think the task is exactly right for a beginner because you've got the legacy service as a backup to keep along if things go wrong. So it isn't too bad in case the migration project goes to waste. Plus you basically have a working blueprint to copy the logic from. It's kind of a typical junior task tbh.
same. the fact that college goes through difficult CS concepts but barely touch the most basic things in development is an embarrassment
One thing I learned from working in tech: Reflection addiction
Doing stuff gave me feedback, it was my job to interpret as much of that as I could, and reflect on it
I loved this. As someone in my first year as a swa this is great for me.
not luck. You went out of your comfort zone, maintained composure in a stressful situation and you were proactive ( knowing ahead of time how to view the latency of the microservice )
opportunities fall upon everyone. Perhaps unequally but the point is to be prepared for when they arise.
Nice breakdown. I can tell about my Google experience: Joined as junior. Team is pretty competent but stuck running extremely fragile system in prod (fires everywhere, touching stuff is scary, infra keep getting deprecated forcing lot of migrations). First project is a manager's pet project that was never feasible, I have nothing to show after 6months. Manager quits after 9 months. I still don't have a project and now under a new manager, I'm stuck doing tedious cleanup that nobody wants to do for another 6 months. 16 months and I have nothing to put towards promo. Finally get assigned to a 2 person project with L6, but I'm able to contribute pretty much equally. 26 months in my Google career, the project is pretty much done (and good quality) but it's not launching because of politics. I still haven't launched anything and quit b/c I'm a little depressed and feel that promo is impossible.
Man, I'm proud of this random dude. That was some good insight, thank you!
Great story! Thank you for sharing this!
You showed your ability of critical thinking and problem solving. Comparing latency of your new system vs old one made perfect sense.
As a new member, the balance of what question to ask and to not ask is the no.1 challenge throughout my career
Well said. I am neetcode. God damn. Oftentimes, I said the same things to myself.
Cool story! I was expecting that you'd be extinguishing all kinds of alerts and weird bugs for the following weeks, rolling back and rerolling infinite times. Neet job making it work from the first try!
Sometimes( a lot of times actually) will is as important as technical skills
Good that you acknowledge your luck.
Great video - Thanks for sharing
wow really like the story
great story!! Keep it up!!
Thanks fam!
Going through same shit and I want to quit.
Not giving up anymore ... :-)
He's that guy. Goat
"I was actually able to deliver that project, by the grace of God." 😁
Tbh, this is a typical junior project. You have a working legacy system as backup in case the migration goes to waste. Plus you have a working blueprint to copy stuff from. You basically just need to copy an existing service of the new tech stack and migrate the logic into it. A capable junior with potential should be able to dig into the problems and grow.
Nice insight 👍🏻
What is your work setup? chair, table & mic etc
Awesome, love a good neetcode story, thanks for sharing
Cool story, Do a honest roadmap story without adds for self-taught developers.
You're a great speaker. How did you learn to do this?
I'm interviewing now and this sounds like a perfect story to share during an interview.
I wondered the same thing. I think it's achievable with enough practise and, as he said, "will" to tell a perfect story in behavioural interviews.
First Comment
Always wanted to do this 😂
You are very talented. Why dont you use your software skills on solving humanity s most important problems such as energy, food, water and diseases?
Good point. But if I can teach CS concepts to 10 people, maybe those 10 people will go on to solve those problems. I feel in this position I can be a positive multiplier.
@@NeetCodeIOGood one ❤
My friend joined Tesla Energy as a SWE last year, switching from data analyst to SWE by following this channel. Totally agree with the positive multiples
What does design doc at Google look like?
Grace of god indeed!
the fact that you only where doing leetcode for a year is so crazy to me
it explains a lot about whats wrong w me
Do you have plans to go back working in a corporate setting?
If you have the will, how can you possibly fail?
Got promoted and then left Google.
Ultra Ultra Chad.
did u do a lot of googling and copying and pasting and searching stack overflow?
Can someone please what tool he is using for the sketching
Hey! I was plannning to make my own Load Balancer as a project. Could you provide me with some guidance. I'm Appplying for SDE-1 jobs and felt like this would be a nice project
so when is it good to ask for help and when not to?? what about those times u don’t ask for help and cant do it independently?
If you think you are progressing with your task today compared to yesterday, then you're in a good position to explain why the task you're assigned to is taking time to the tech lead / manager. If not, there's no point in keeping it to yourself. Alert the team in the stand up meeting and try to resolve the issue with a mob programming session.
Don't hesitate asking for help. Even seniors get stuck. Most companies encourage asking for help when you feel like you're stuck. I'm not sure if a company that discourages seeking help is a good company to stay. It's a sign to leave.
What tool is he using to draw on the screen?
9:37 for TL;DW
Is that guy is Techlead ?
Jr dev: afraid to ask questions
Manager: you're so independent
> gets work done without asking questions
That’s the main part 😅
Any advice for someone whose degree taught them R, works as a database engineer using SQL Python and Java (Talend) for ETL, trying to get into full stack development/systems?
What does he use for board drawing
They had blocking code at Google? Seriously? At Google?
But there's also a guy who back up as you said in the video
you got promoted in a year then left after a few months?
yeah its more common than you might think to leave after promo
based
It's glasses. Men always look smarter in glasses 😜
indian roots visible