Yes, I just liked my own comment

Sooo, at the moment you aren’t in Netflix?

@@ThePrimeagen narcissism at it's finest 😂

I just saw it as clickbait. It's cool, everyone does it, gotta beat the algo

@@akbarnurullaev7918 I am at Netflix. I said there, which I probably should have emphasized a lot more, that. Jeff Wagner, a previous boss and the man who hired me originally, made me an offer to stay.

I have enjoyed taking down production.

@@ThePrimeagen 😁 you were having fun with production code right?

Testing is a waste of time, when you can more efficiently get immediate, detailed, angry feedback from your users.

Let's face it, if you haven't brought PROD down then you're not a real dev.

Scary at first? No doubt, but then it becomes an achievement.

This did take place quite a few years ago. But there's always time and places when things become difficult. This just became difficult and then stayed difficult

I work at a fortune 100 company and its exactly like this, w/the turnover that goes with it. The 'big company' is just an aggregate up of small departments/divisions that have their own budgets that usually doesn't go far enough. AND you have to comply w/the non-coding architects' mandates.

If you’ve ever worked in a big corporation, you’d know they’re really inefficient. They have the budget to throw money at it. They hire people to create the idea, standards and training of a new project and none of those new hires have any clue about ABC and why XYZ won’t work but they have degrees that say they do.

@Veronika Zaglotova Yes, it depends on multiple project factors. How long to go? How many seniors are on board? How at capacity are they? Are you training people who are experienced? If you had one senior and they were overloaded along with the rest of the team, something has to give. The short term managerial solution is to push the senior and reward them with oodles more compensation... but for the wellbeing of all, extra time needs to be allocated, either/both for training new staff or just giving more time to existing staff to fulfill requirements.

@@ThePrimeagen From how it sounds, you became the Go To Guy for Groovy, which makes a bottleneck. Knowledge sharing is a big deal where I work, so the whole project doesn't stall if someone becomes sick/on holiday/leaves.

Thank you. I totally agree

I was in a situation like this and yes being honest and professional is important. As a junior engineer I was still emotionally immature from a pretty traumatic upbringing and my communication skills were severely lacking. I was working at Facebook as an E4 in 2017. This really cool idea that I and other people on my team (Web Speed) had been thinking about came up. It was basically OpenTelemetry's "Zones.js" concept but with reference counting added on top to be able to automatically track how long an interaction takes. I don't really know how the implementation of the project started, all I know is one of my senior coworkers dropped out of the project so I was asked to take it.... Boy oh boy there was a a reason that other engineer dropped out. I should have asked. Basically, the other junior engineer on the project was writing extremely complicated code which he covered in dozens of tests which made it very hard to say to him "Hey are you sure this needs to be this complex". Anyways, a week into the project I'm trying to use his prototype and it's not working.... he tells me I must be using it wrong... I spend a whole week digging into the convoluted logic and after a week I tell him "Hey I thinks there's something missing here", to which he replies "Oh yeah, I accidentally deleted a line before committing".... Facepalm. Needless to say the relationship was extremely passive aggressive from then on. A year later he gives up on the project, I take over his side and in two weeks I figure out he made a fundamentally bad assumption in the very first PR of this whole project, which my teammate approved right before leaving the project. Anyways a week or two after that I made a bug while changing some part of the system it was a minor bug but significantly impacted performance metrics for a particular team. After that all goodwill with customers was lost because the project had been out for over a year and still wasn't stable. The hard part is that most of the blame was put on me because it was clear I was being passive aggressive toward him. I never told anyone about the 1 week thing because I thought it would be "snitching" and wouldn't really get me anywhere. As a result it looked like I was "the problem" with why the project wasn't succeeding. Sure I was part of the problem, but I wasn't the whole problem. Who thought putting two junior engineers fresh out of college on a complex project would be a good idea? The more annoying part for me though is that the project finally did work at the end but never got to see the light of day.... and I ended up rejoining Facebook a few years later and there's a team literally with their own project similar to what I was working on.

Hey thank you.

I'm happy this could happen.

@@ThePrimeagen I'm happy you happened

Same here. After three years at any job I get bored and know it's time for a move. I've never regretted the decision in the end.

There may or may not be. I'm always a bit hesitant sharing details of how I took down production.

​@@ThePrimeagenstill hesitant now, Mister? 😏

Hey, that's pretty cool. Thanks for sharing

Cool story, Tommy. How much did performance improve after implementation?

He is too busy upgrading to C++ 20...

It does take quite some time. The hard part is recognizing where you fail. I definitely felt. At first I was 100% in the right and everything else was wrong, but looking back there are always things that could have done better

​@@ThePrimeagen Except you did not fail. I _always_ choose B. I also never ask for raise. Here's my point: my manager makes 2x the money of an engineer, there's no problem with that, until he or she works for it, so he or she should have been recognize the situation. How? Talking with people. They don't tell him/her things? Why your co-worker told to *you* what is his problem, and not to your manager? He was afraid to tell it to his manager? Hm. Also, you're right, if you're a senior developer (as me, 32yoe, omg) you just can't close your eyes and turn your head to the opposite direction. But this is only true for technical questions (I have a method for handling these situations: 1xA, 1xAlert). For "human-related" situations, my manager have to detect and manage(!) shit. If he/she feels that the situation is not shit but deep shit, which he/she can't handle, he/she might ask help from... wait for it... it will be funny... wait for it.... from HR! Let me (senior, 32yoe, fck) deal with fucking product and technical issues, I have fucking enough of them, let me teach and mentor juniors, and don't bother me with things which have a complete department for. HR workers don't write unit tests for me, lemme' not dealing with their stuff, I don't want (and I am not able, being slightly autistic, who can't recognize other's feelings too well, okay, it's my problem). Everyone should do his or her job. You haven't failed, it wasn't your job. Probably, you'd escalate it to your manager or HR.

Yaya!

Lol, complaining is lucrative in the US

@@imagreatguy1250 Yeah that's a fact. Fortunately better content does exist though

Aww that’s awesome I’m happy for you :)

what business did you do?

@@javier.alvarez764 I started a property business and a quantitative trading business.

Thank you. Also the name is prime. Who's this Michael fella?

Some questions don't get answered on this side of eternity. But it is good you've tried to reach out. You have proven to be wiser than me

I wish I could have been that coworker

It's so hard these things. Especially when you're young. I'm happy I went through this experience because it has changed me. But it took a couple years to really settle in.

yeah, its always hard looking back. it feels like i just know so much better now :)

That's good to hear. I did not have this when I was younger, so I'm happy that you do

I get that. And this is all good stuff here. I am happy that ultimately I transfer teams. And from their life became way better.

That's pretty awesome. Ultimately the same thing happened to the individual team. It was broken up and the products were no longer offered. Sometimes there's nothing you can do

dude! pretty much same!!!

yayayaya!

Netflix as a whole is pretty great. But like all companies, there's always dysfunctional parts

I just had to change teams. I quit Netflix, but then a friend of mine pulled me onto another team.

@@ThePrimeagen if it's a contract thing and moving teams ain't really a possibility for now, should I try and improve things or just invest the time on good learning for myself? I want to contribute but it feels like they're just coming to clock in the hours

@@d_6963 exactly. by leaving it'll hopefully send them a message in the future. bad workplaces in effect work kind of like the free market (when you're at op's salary). If the company mistreats or overburdens workers and they leave, they'll either change their working environment or they'll forever have to settle with less talented/inefficient employees as that's the only people they'll retain.

Only advice (apart from leaving, which you should strongly consider) is when you're asked to do XYZ by next week go "no problem boss" then give them a few sheets of paper of your responsibilities/tasks you're currently working on and say "which 20 of these things would you like me to put on hold while I make this new feature of yours?". If they refuse to play ball and tell you to just add it on top then you hand in your notice the next day.

Re: "I'm really happy to hear someone with your talents landed in EduTech." He got the offer with Coursera but went back to Netflix (see video).

I don’t remember who originally said it but “You have two choices. Change your job, or change your job.” Meaning, you can try to work with your company to make your job better, or you can go somewhere for a better job. It’s often suggested to try to do the first as it’s typically lower risk. But after that fails the second is always a backup plan. One last reminder. Every job has sucky parts.

It's funny how that works. When you're young. You feel like answers come so quickly, but as I've aged answers come slower

@@ThePrimeagen I think I am noticing this as well with the help of mentors in my life (including you). The world and people are complex and you only have your point of view, but I can at least get better at illustrating that point of view so it applies to the goals of others (understanding managers goals, dev team goals, etc...)

yayaya

Thank you

Yeah, even all these years later it's still resonates with me. It's hard to get over these things.

As a tough situation. I always have a really hard time with that type of boss.

@@ThePrimeagen hmm 🥺 I feel sorry for you. Hope no one ever really gets such a manager!

@@ThePrimeagen Just got a little sad yesterday after watching the video thinking someone as talented like you had to go through this. I hope my previous comment didn't sound negative in any means.

In my opinion, don't just be open about how things are bad technically, if toxicity and saying shit behind everyone's back is something that is happening. Try to improve the team mood somehow and say out loud that this toxicity is affecting not just you, but everyone even if they don't notice it. If still, things don't improve, do leave for your own sake. Boa sorte, mano!

:) ty

A good mentor can help a lot of problems. And I do agree with that

Such a fact, Eddy. What I end up finding is that if I don't speak up, I end up blowing up. I communicate in a rough tone to someone who doesn't deserve it.

Hey, you're already thinking about these things. You're ahead of me

Thank you

Minimum be there for your coworkers. Whether you choose to leave or to stay, be an encouragement when you can.