나의 넷플릭스 그만두기 이야기: 번아웃, 소통의 실패, 그리고 배운 교훈

### 넷플릭스 탈퇴의 여정: 소통과 자기 성찰의 교훈
* 🎥 넷플릭스에서 일한 지 3년이 지난 후, 저는 많은 사람들이 기피하는 **그루비 프로그래밍 언어와 관련된 도전적인 프로젝트**를 맡으며 뛰어난 성과를 거두었습니다.
* 🚀 저의 성공은 **비디오 메타데이터를 개선하는 중요한 프로젝트**에 참여하게 되었고, **GraphQL에 비유되는 Falcor라는 오픈 소스 이니셔티브**에 참여하게 되었습니다.
* 🌍 컨퍼런스와 오픈소스 커뮤니티에서 연설하는 것이 즐거웠지만, **소규모 팀워크와 코딩을 하지 않는 아키텍트의 존재**로 인해 업무의 현실은 점점 더 힘들어졌습니다.
* 😩 주당 60시간씩 일한 지 1년이 지난 어느 날, 프로젝트 피벗에 대한 대화를 나누던 중 **더 이상 스트레스를 감당할 수 없다는 사실**을 깨닫고 한계점을 경험했습니다.
* 🤝 힘들어하는 동료와의 상호작용을 돌아보며 **팀 문제를 해결하는 데 좀 더 적극적으로 지원하지 못한 것**을 후회했고, 이는 **새로운 직장을 구하기로 결심하는 데 영향**을 미쳤습니다.
* 📅 결국 친구의 추천으로 코세라에 입사하게 되었지만, **넷플릭스에서의 여정은 소통과 이해의 기회를 놓친 채 시작**되었습니다.
* 🗣 때로는 경영진과의 열린 대화를 통해 변화를 이끌어낼 수 있다는 것을 인식하면서 **직장에서의 어려움을 말하고 해결**하는 것이 중요하다는 것을 배웠습니다.
* 💼 5년이 지난 지금, 저는 여전히 **넷플릭스에서 일하며 과거 경험에서 얻은 교훈**에 감사하며 계속 성장하고 있습니다.

소통이 원활하지 않고 지원이 부족했던 저자는 넷플릭스를 그만두게 되면서 적극적인 팀 토론의 중요성을 강조하게 되었습니다.

So this is the story about how I quit Netflix. About three years into working at Netflix, I was kind of excelling. I took on some projects that a lot of people kind of said no to. It turns out that we had Groovy on the back end.

Groovy, baby, was on the back end. It's a terrible JVM language; it absolutely is dog water. But I just happened to take a little bit of time, look up a few things, you know, a few ways to do stuff in Groovy, and of

course, I just excelled beyond everybody else because everybody else is just like, "I just want to get the stuff done. I don't want to look at it; I don't want to be a part of it." So I got good enough that I could actually build a bunch of

different back ends. So I got selected to kind of do this kind of large improvement that would make it so that we could have extra metadata about every single video in the television catalog. And of course, from there, they put me onto an open-source project that was

related. It was called Falcor—no, not the Luck Dragon. Okay, though, named after the Luck Dragon, not *a* Luck Dragon. Effectively, what Falcor was is you can kind of think of it like GraphQL. You provide an array of kind of strings or numbers, and it would go off onto the

back end and grab all that data—like a super simplified SQL-like language. Yes, I just said SQL. Hey, I'd also be squealing if you hit that sub button! Thanks, baby! Anywho, so this was like my dream job. I got to go to conferences; I got to speak

Both in the UK, I got to speak, uh, multiple times in Amsterdam, got to do a bunch of different places throughout the United States. It was awesome, open-source circuit, the dream life, right? It was fantastic. Actually, it wasn't that fantastic now I think in

today's day and age, that that really is the dream life; that is what a lot of people kind of aspire to: working full-time, getting paid, while working on open source. But let me tell you, I, I would—I really had a hard time, and this is the reason why we are a

small team, about four of us devs, all working on a couple different products for the UI kind of team. We were called a UI platform at the time, and during this, one of the roles was kind of like a non-coding architect, really deciding how things should work, and of course,

this role kind of appears from various companies, and people really have strong feelings about these kinds of roles. Me personally, I greatly dislike non-coding architects. The reason why is I feel like they get so abstracted from reality that they start building things that, though

they look great on a whiteboard—we're talking lab coats, *mwah*, clipboards, those little goggles to protect your eyes—things are looking great, but when you actually implement it, it's nothing but a dumpster fire of logical inconsistencies and all those other things. I just, I just

can't stand it. So, of course, this was going on, and for about a year, I just—like I was programming like 60 hours a week. I was putting in so much effort, and it was just starting to feel more and more soul-crushing, and I can still

Remember, it must have been December 27th, 28th, or 29th, shortly after Christmas. I was walking into my backyard at about 7 pm, having a long conversation I didn't want to have, discussing some internal details about Falcore.  Oh, we want to make this...

pivot. Oh, this is actually going to be the greatest, most ergonomic, most developer-experience-changing thing in the universe! And I remember that was kind of the moment I snapped. Like, I couldn't handle this project anymore; I became pretty darn infuriated with it. But at

the same time, something else happened. I had another coworker working beside me who was also feeling a lot of the same weight, and he really reached out and started pouring out his heart, you know, in the best way he could. And of course, I was

much younger and much dumber at that point, and I didn't catch it at all. I was just like, 'Yeah, I'm kind of upset too,' but that's about it. I didn't hear him, and I really look back at that

as one of my bigger failures at that moment, and really, of my lifetime professionally.  You know, having someone come to you and tell you these things and not really try to be there for them, try to help lift them up, or even approach your boss—with

their permission, of course—and really try to create a better team conversation... I really wish I would have taken control of the situation.  I would do things much more proactively and openly today. Long before I got to the

Point but ultimately, what ended up happening was that I became so sick and so kind of toxified from my job that I started looking elsewhere, and ultimately I did find a different job at Coursera. Yeah, Coursera, online education. I had a good friend there, Tom Willow,

where we were... who was the... I forget, Chief Product Officer, something like that; Vice President of Products. I can't remember what his role was, but he got me the interview. I got accepted. I was actually going to make the jump, and I sat down with my boss and said, "Hey, I'm

not going to work at Netflix anymore." And ultimately, it was all because of those previous interactions, and I think there's a lot of things that I did that I failed there. I really do wish I would have taken more time and understood how I felt and kind

of really, you know, judged myself in a more sober tone. And ultimately, I really wish I would have been there more for my coworker. I really wish I could have turned around the team and helped, because in the end, a couple of people, you know, within this area—actually a few

people within the area—got fired, which is sad. I was about to change jobs until, of course, Papa J Wagner came over and called me back in, made a nice offer—no monetary, by the way, no monetary change—just made an offer for me to come work

with him on his team, and ultimately I did, and it was fantastic. I took down production a few times, and it was a lot of fun. But in the end, I quit Netflix, and it's because I didn't have the communication and the talks that I should have had. I wasn't understanding

myself as well, as I should have. And so if you find yourself in those situations, you've got to speak up. You've got to approach your boss, and if your boss and your coworkers aren't good enough to listen—like I wasn't good enough to

listen—right? You know, I, I, I failed my coworker, but ultimately my boss should have also been there, listening and making the situation better, which didn't happen, and it led to a lot of, uh, you know, probably a lot of heartache. If you work at a company that

doesn't support you in that kind of sense, that doesn't understand that things are kind of going wrong, that it's only causing more and more tension, you probably need to start thinking about: a) how can you improve the situation? Or b) is it time to leave the situation? And I

just chose B without considering A—big mistake. Make sure you consider A, because often, you know, bosses are motivated to make you, you know, happy; they're there to make a team successful. And so there's a lot of change that you can enact by simply speaking up and being

confident and pushing forward what you think is best. So that's the time that I quit Netflix, but hey, I still work at Netflix! I still really enjoy it. That was about five years ago, and look at me now: I work on dumb things and write C++

from time to time. Thank you for watching! Hey, subscribe to the channel already! Give this video a like, maybe make a little comment: Have you ever had a situation in which you affected change you wish you would have, looking back? Or have you ever been on the other side of it—the firing side?

The side in which you wish some other coworker would have stepped up, like I should have done for mine. My name's [Name], thank you.

Why I Quit Netflix

ThePrimeagen

넷플릭스의 초기 성공과 팔코 프로젝트

넷플릭스에서 남들이 기피하는 도전적인 프로젝트에 참여하며 초기 성공을 거두었습니다.

다른 사람들이 꺼려하는 그루비 프로그래밍 언어로 작업하며 뛰어난 성과를 내고 있습니다.

동영상 메타데이터를 개선하는 대규모 프로젝트에 선정되었습니다.

GraphQL과 유사한 오픈 소스 프로젝트인 Falcor의 후속 작업입니다.

컨퍼런스 참석을 포함한 꿈의 직업에 대한 즐거움.

팀 역학 및 워크로드 관련 과제

코딩을 하지 않는 아키텍트와 소규모 팀에서 일하다 보면 불만이 생길 수 있습니다.

현실과의 단절로 인해 코딩을 하지 않는 건축가를 싫어합니다.

과도한 근무 시간(주당 60시간 이상)과 영혼을 짓누르는 압박감을 느끼는 경우.

팔코 프로젝트에 대한 좌절의 결정적인 순간.

동료가 비슷한 부담감을 표현했는데, 발언자가 적절하게 해결하지 못한 경우.

동료를 지원하고 상황을 적극적으로 해결하지 못한 것에 대한 후회.

더 나은 팀 대화를 만들고 통제권을 확보하지 못한 것에 대한 반성.

직무 불만족으로 인해 Coursera에서 새로운 직장을 찾고 있습니다.

넷플릭스에서 사임하고 과거의 소통 및 지원 실패에 대해 반성합니다.

팀원 해고를 포함한 상황의 결과.

넷플릭스의 다른 팀에서 반대의 제안을 받았지만 결국 그만두게 되었습니다.

적극적으로 문제를 제기하고 해결하는 것의 중요성.

떠나기 전에 상황 개선을 고려하도록 조언합니다.

상사는 성공적인 팀을 만들기 위해 동기를 부여하고 열린 소통을 장려하는 경우가 많습니다.

지난 5년을 되돌아보는 넷플릭스의 현재 고용 상황.