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
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.
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.
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!
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
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?
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.
