@daniyalmujtaba
"I took down the production a few times" actual true definition of fun job for dev
@TomNook.
It's surprising to hear even a big company like Netflix are letting staff become so overburdened. Even my small company realises that you can't put too much on 1 person or team. Hire more people, cut features or lengthen deadlines.
@tsdecker
Not just clickbait anymore
@ghsinfosec
I've realized over the years that being open and honest in situations like that can really turn things around. Though painful, they are certainly growth opportunities both professionally and individually. Great story!
@DavidWoodMusic
I really appreciate this. I'm on the verge of putting in my two weeks at my current position and this brought some great insight.
@jackmonkeyca
Something definitely changed for me when I went through a little burnout in a previous team and it's maybe because i saw it happening in parallel with someone else. I realised that the people I work with are humans and for the most part care about me a lot more than the company I work for to whom i'm mostly just a number or statistic. That's perhaps a bit pessimistic but I always need to remind people to look after themselves because the company isn't gonna do it for you.
@ryanleemartin7758
Really appreciate the honest reflection of professional failures and struggles for everyone to see and learn from. You're a damn good egg, sir. Also, "I took down production a few times and it was fun" I can only assume will be a forthcoming "Storytime with Prime" video.
@0runny
I truly sympathies. I too went through something very similar, but my boss didn't want to know. He was such a crap, back stabbing, scheming idiot that I left. I was so motived that I started my own business in an unrelated field. I can now work on what I want, when i want. I now code, not for a job or a boss, but for pure pleasure - it is the ultimate gift for which I'm eternally thankful.
@jupyter5k647
That was some real good piece of advice that I had thought similarly of multiple times the last year but did not had the perfect wording/condition to try to put out there. Thanks for putting it out there 👍
@pelom2905
At a similar crossroads right now. All these tech courses, videos, articles, docs etc... None of them teach or cover the people side about being in the industry. So am grateful for some perspective here, and have really taken something away from this. Thanks
@pedrohakia1
This is gold, Thank you so much Michael por having the strengh of telling us how you feel, and how we could improve as well in our own jobs. God Bless you my friend!
@ColinDdd
this SERIOUSLY is a great video mr. primeagen. i feel like i got so many parallels to your earlier career, e.g. doing open source, invest tons of personal time to try to make cool stuff happen, but also have a non coding manager and really hate it sometimes...really good tips and it takes serious work to learn and internalize those emotional lessons
@za_wavbit
Sounds like the reason I quit my first long-term tech job. Over five years I gradually became the senior-most engineer there (YOE at the company, not in the industry), and wound up spending two years without a single day off (including weekends and holidays). Couldn't deal with it anymore, didn't learn to say "no," and eventually I just noped out. It didn't help that I was the guy who had to pull creds through a few rounds of layoffs (which is super emotional!), or that the C-suite kept changing every few months, or that we were dealing with a lot of legacy code from the early startup days. In retrospect I wish I could've had more time to prepare my team, but I did at least spend about a month just documenting the architecture (since I was the one who designed a lot of it).
@Muaahaa
I had one of the most skilled members of my team confide in me that they were in a situation where they were serious unhappy in their role and actively in talks with another company. I pretty much pivoted my plans for the next couple weeks to meet with them regularly to see if there was something we could do to change the dynamic in our department or create a new role that would excite him. I was not his boss and couldn't make any executive calls, but out of our discussions came some ideas that he did eventually take to his manager, who was very eager to make it work. I believe that if we didn't have all of those discussions he wouldn't have brought anything up with his boss besides giving notice.
@markvaldez8602
Very interesting perspective! As someone who just started their career, I don't feel like I completely understand but when you mentioned the two options that made a lot of sense. That advice to see if you can fix the situation before leaving is great for other things in life too (sport teams, relationships, etc).
@LyleTroxell
Poppa Jeff saved me a couple times at Netflix too. And I remember that time at Netflix when you were working/arguing about Falcor. We had adjoining cube walls! Great story Prime, thanks for sharing it.
@metacrng
I think this kind of advice is priceless for all the junior engineers out there. Thank you Prime for sharing your experience!
@BrendonOtto
Been going through some of this at my job and spending time with the people on my team having the hard, sometimes uncomfortable conversations is the thing that turns it around for everyone. As tech focused individuals most take solace in the tech side but the people side can be really rewarding too :)
@michaelsydenham2918
Thanks for an inspiring story. This pretty much sums up the importance of emotional intelligence in the workplace (which is not easy to acquire) and also the value of (honest) self-reflection. Often our work is not just coding or working with peers, but also just simply 'being there' and having supportive conversations during tough times in a project. The best managers are attentive to these issues, and manage it well (= good outcomes).
@ThePrimeagen