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.
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.
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 ๐
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.
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).
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
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!
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.
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).
Just came across your channel today bro ๐๐ป I myself had a decade of experience under my belt and still felt like I struggled. Here 2 years later Iโm still struggling BUT Iโm able to build huge projects like a social media. I love your take on programming and I now have to consume all your content. Your awesome dude ๐๐ป
Thanks for sharing. Recently found your channel and loving it. Thanks for mentioning the time about a former coworker. I had a coworker commit suicide while at work. I had no idea he was struggling. Itโs important to prioritize people and relationships over projects and deadlines. I would like to find or start a company that lives these values.
I walked away from being a high school teacher because I did not know how to ask for help from my supervisors. I let those toxic feelings swell until I snapped. If I could do it over, I would have spoken to the principal and told him where, how I was struggling. It was a great lesson to lean into the support systems intrinsic to healthy hierarchical relationships.
being a software architect without writing code urself was a huge part of my degree. It was only in the end when we got more and more into actually programming the stuff that we were designing that I realized, that they were teaching us, that being a software architect that doesn't write code, just simply does not work. It only works on a very abstract level. Once someone defines classes, interfaces, properties, types and so on, that's where it just stops working, because there will be at least 1 logical inconsistency that breaks the entire house of cards
I came to my big company job with a lot of ego having pretty much controlled and designed everything in my previous job for a decade. It's crushing to find yourself in a dysfunctional team with out of touch leaders and know that you're working your ass off to make something worse. But these companies are big and one team is not like another, and as software people we have the luxury often to request a transfer. So if it's been a few months and that's how you're feeling, you gotta ask to move and don't let a middle management person convince you to stay "because things are just about to get better" as that's how you get angry and mad and feel trapped. There aren't many other jobs that have to make efforts to please their employees when they are thinking of leaving, we have precious mobility and bargaining power. But we're also an industry filled with meek individuals that dislike conflict, suck at demanding compensation for OT, and often do a bad job of looking out for each other. Remember senior engineers, any bs you're willing to put up with for your paycheck is bs * 2 your juniors have to put up with for less, because if you can't say something they have no ground to stand on. We're in this because we love programming and the world needs programmers. Honestly we work best when we have some autonomy to execute the businesses needs, we deserve a little ego for being able to do it, and we need to stay a mile away from consultant types that don't write code or don't get business goals accomplished. You can't design if you don't use the code you're designing. whew what a rant, hits a nerve lol
Communication is everything, whether youโre an employee or manager, 90% of workplace problems can be avoided by better communication!!
I was a hands on manager of a cloud infra devops team at philip morris until all the burocracy, architects "Security" people (no actual security skills), pointless IT controls burnt me out. I barely was sleeping, I was sleep talking and fighting with them in my dreams, it was quite bad. I decided to step down to a full time devops engineer, which is what I enjoy, and I was lucky a friend of mine step up to the manager position shielding the rest of us from all that crap. I didnt quit per-se, but I kinda did, however now I do full time what I like with almost none of the torture of having to deal with those other areas.
Great, relatable story that has earned you a sub :). Out of prolonged frustration and anger, we all too often tend to pick option B without considering option A for a second. Easier said than done, and this video definitely comes as a great reminder to all of us :)
Great to see some honest personal content out there that will likely resonate with most people working in a team.
Love these videos. As a junior who does not have a mentor, these videos are really a good source of guidance and experience for me. Thanks prime
@ThePrimeagen