I've been a software developer for more that 15 years and my biggest piece of advice is don't be in a rush. Hone your craft and forget comparing yourself to some social media version of the job. You will progress at your own rate. Burn out happens when you try to progress faster then you naturally can. When you start getting too comfortable is when you know it's time to push to the next level.

30+ year systems architect here. I give all my "newb" developers the same advice. Learn to say "no". Learn to say "I need help". Learn to say "I can't finish in time." There is nothing wrong with being human but there is a lot wrong with being stubborn and prideful.

I was afraid of becoming a software engineer because I knew it would be stressful at times. It was and still is stressful. Burnout, imposter syndrome, exactly is the way I feel and I've been a developer for 18 years. On the bright side, I've taken a majority of my money over the years and invested it wisely. I'm planning on getting out of the industry all together by the end of 2023. Life is too short to have this much stress all the time.

I've been an engineer for over 10 years, and my biggest piece of advice for new engineers is that you have to prepare that its going to be a GRIND to go from zero to being a professional level programmer. Its HARD to learn how to code, like REALLY hard, and you are going to often be very frustrated while you're working through bugs and learning how a language works. Don't give up! As long as you keep grinding through the problems, you will make it

Take it from a guy who's been in IT professionally for over 25 years and a computer addict for about 40 years ... KNOW YOUR LIMITS AND EMBRACE THEM! Along with that is NEVER apologize for being you. The truth is that your skills are needed and there is no foreseeable end to that demand at this time. That being the case means that you'll always find work and you need NOT be someone that a corporation expects you to be. Learn how to shut down the laptop at 5pm because when it all boils out in the wash ... no one ever said on their death bed that they wished they had worked harder - FAMILY IS FAR MORE IMPORTANT THAN WORK‼And I cannot say that enough nor can I stress it enough. If you do not TAKE THE TIME EVERY DAY and spend it with your family, you have no idea how quickly 40 rolls around and you look behind you and you realize that you missed ALL of it because you were trying to be what someone else expected you to be and for what? A few extra bucks? ITS NOT WORTH IT - TRUST ME ITS NOT WORTH IT! If someone at work wants to make demands on your time after 5pm ... you have to simply tell them "I'm sorry, but I have plans with my family" and you have to say that EVERY TIME ... could it mean that you get looked over for a promotion? ABSOLUTELY IT MIGHT ... but what good is money when you're living by yourself? Or what good is money when you miss the most important times in your children's lives? Cause man... I'm telling you ... all the money in the world could NEVER replace those moments that you can NEVER go back and get ... and children grow up so damn fast its insane and if you don't force yourself to step away from the corporate greed for your time ... you'll piss it all away and you'll regret it for the rest of your life and living in that kind of regret is a hell all of its own... Work to live ... don't live to work - and that's not some coined cliche' ... those words should dictate your life - literally!

Being a software engineer is so mentally exhausting. I don't think people realize just how hard it is to recover from mental exhaustion in a field that rarely gives you a break from working at full mental capacity all day everyday.

I just want to take a moment and think all the folks on here who have been in the industry for so long… Freely given away great advice… It really helps Junior developers like myself navigate this technology space and really learn what areas I need to be focusing on… You guys are the real heroes

In my 24 years of experience. As a developer, engineer and now architect. Once you have experience and are able to hold down a job and take on the challenges, you are good enough. Furthermore, don’t allow your employer dictate your hours. Lastly. I cannot stress this enough. Stay a tech expert and don’t let any employer make you an expert in their problems.

I’ve been writing code over 20 years now... still feel like an “impostor” sometimes. This man speaks the truth. Bravo.

Here in Japan there aren't many companies that do a technical interview. The culture here for any position is that you learn on the job, so most companies are happy to hire you even if you have zero experience. And for that reason they also expect you to be pretty much useless for a year or two. I always liked this because it gives you time to slowly learn the skills you need, while getting fully paid!

As someone seriously considering becoming a dev (including choosing software engineering as my major in college), I really appreciate these kinds of videos. Burnout and the pressure to constantly learn is something that I've already felt a little hint of with my summer internships. I also really value my personal life and free time, and my dream is to get a remote dev job so that I can travel the world while I work. My dad (a front-end dev) has given me the advice to always be careful with promotions and advancements, as these can lead to the sort of high stress and pressure that you've laid out in this video - with little to no extra pay. Again, every job varies in terms of stress, but we should always be careful to avoid extreme burnout and stress in our jobs, even if it results in a lot of money. The old proverb is true: Money doesn't buy happiness.

I'm a senior dev at a large company (not FAANG, but at that sort of size). For us, as you move up you spend less time coding and more time in the abstract. I enjoy doing design work and solving abstract problems, but man when I get to write code in a sprint I am on cloud nine. For you junior devs out there, enjoy your time in the weeds, but keep the balance. I gave up a lot of personal growth in my 20s chasing a better career, and even though I hit my goal I wish I had spent more time with myself and my family.

Thank you for this, it's all true. A few things I've learned in over 25 years of being a software engineer: 1. Being able to write code fast is not the same as being an expert software engineer. Expert software engineers think about how their project will look years from now, learn from their mistakes and design in flexibility, security, and scalability from the beginning using best practices, standards, and design patterns. That takes more initial time and effort, but it pays off over time in so many ways. Your boss probably won't understand that -- they just want "fast", so explain it to them. If they don't care after a few attempts to explain the value of this approach, you are probably not going to further your software engineering skills much on that project with that boss. 2. Don't be afraid to ask your own questions when you are being interviewed. You can learn a ton about whether the team and company are a toxic environment or a supportive, positive environment just by asking a few questions. For example, how do you handle technical disagreements, how do you further the skills of developers on your team, how are decisions made about promised deliverables and timelines (you want them to tell you the team is consulted). If they are put-off by these questions or the answers don't sound good, you probably aren't gonna be happy there. If you don't hear good answers don't be afraid to pass it up, there are some great companies and teams, and a lot of not-so-good ones with ridiculous expectations. 3. Find a body-based interest outside of work: yoga, meditation, strength training, fast bicycling for me, and bend your work life to fit around that. It will keep your mind sharp as you get older and help you be calm when you are under pressure at work. If you don't do this you will probably become unhealthy over time because the nature of most software jobs is to sit all day and overwork you unless you push back. Don't be afraid to push back. I've worked 40 hours or less nearly every work week of my career, and had a few jobs where I worked 32 hours with Fridays off. You can do that too. 4. There will always be someone on your team or at your company who is faster and better at coding than you, you will still make mistakes after 25 years and it's rare that you will do perfect work the first time. Be kind to yourself, pay attention and learn from your mistakes, let go of comparing yourself to others, keep learning (but don't obsess about constant learning). Find your unique strengths and use them to your advantage. For example I discovered I have a knack for designing user interfaces even though I'm self taught in that, so I'm the go-to guy for U/X and I co-design U/X with a classically trained U/I expert. Find your special power.

I've been a software engineer for like 14-15 years, I lost track, but there is one piece of advice I could give to anyone. Always estimate your tasks at least 2x or better 3x than you think the task will take to finish. Don't be that guy who underestimates everything and then works after hours to meet the deadlines. And you will be overflood with "side tasks", management will take advantage of your work pace. The world will not burn when you won't make something on time. I know, no one wants to lose their job. But companies don't want to lose good programmers either because of one fault, one misjudge. Also, when you are done, you have done that day. Don't check your email, don't respond to any Slack messages or whatever you use. You are done and you have free time now! Otherwise, you will have that feeling that you are at work 24/7 and burnout will come really fast.

It's good to see that others feel the same. I started wondering if I was the only one that felt this way because I am surrounded by people who seem to live to code. I have been the lead (hands on) engineer at the 3 companies I've worked for. It seems like I am the only one who cares for a work life balance, which makes me feel guilty even though I know it should not. We always deliver but since there is always more to do, we just feed to the infinite void. And, every time I try to switch jobs I am reminded that the interviews are completely different, and it feels like im back in school again. Seems like a never ending battle.

You seems to know exactly what I needed to hear. Very well laid out and said. Burnout and mental health issues are a real thing, and somehow we all need to be able to cope with the challenges and have a proper life outside work. I now believe seeking for healthy work life balance should be the key component in what to look for in anyone's next job hunt. Anyway, thank you for your rather therapeutic video. Cheers!

Its comforting as a junior developer seeing all the advice from experienced devs in the comments. I feel parts of the internet portray this mindset of grinding day and night.

Something that’s really not talked about (or thought about) enough is the morality of software we create. Coming out of uni and being thrown a tonne of cash is so enticing but ‘waking up’ five years later and realising you just helped make some shady surveillance software that actually messes people up, is something that no amount of money will help with your conscience. It sounds whacky but I really think we need to hit the brakes on software, sit back, really think long and hard about what it actual does and where it’s going and then build something based off of real values and morals for the whole world. Not just super wealthy control freaks.

I was a programmer (as we typically identified ourselves) for 45 years. I never wanted to take the typical path into management because staying close to the machine felt like it kept me honest. My ability to face a problem with curiosity, wry amusement, and willingness to live with ambiguity kept me in the game. Over time, though, the burden of years of minute and particular knowledge grows. You have to dredge up things from years before, reassemble the context in your brain, and then try to evaluate if essential conditions have changed. Believe me, the next big thing is the easy part. Supporting all the last big things is a bear.

Here's an angle i haven't seen mentioned. Programming well actually requires a negative mindset. Because you have to constantly be thinking 'what can go wrong' and cater for that. It's always working out the worst case scenario and focusing on it. Often i find myself in risk management mode, rather than being creative..because breaking the system is worse than producing something pretty.

I've been programming for over 20 years. I am 50 now and the I one thing I regret most is that I spent so much of my time coding whether at work or at home and not enough time with my wife. I only realised too late after my wife passed away that it wasn't worth it. I love coding, but @Gyasi you are so right that no other field expects you to be constantly updating your skill set. It's an amazing field to be in, but it can take over your life. Peace fellow programmers.🖖

Nice video. I'm an aerospace engineer...so not exactly the same issues, but similar. Interviewers are often unrealistic about what skillset is even possible. If you are an expert at computational fluid dynamics....it's unlikely that you are also an expert stress analyst. Then there are some guys who hyper focus on their career and professional skills and *shocker*, they have personality and behavior issues because they have no life outside of work. It was best explained to me by a former boss: "When you die, your gravestone isn't going to say that this employee exceeded expectations"

Thanks for this real talk, been burnt out and started the same way you did. Been having trouble balancing this new career while still having a life. I really appreciate this

Great Advice, the big problem with IT field is that it's a rat race. A lot of ITs are pirates. I know my limits and I work at a reasonable pace; however, my competitors will outwork me on purpose just so they can outshine me and my peers who are also working at their own pace. And once the company review happens , WE ARE LET GO! We become unemployed again while the ITs who are working at light speed just so they can stand out ending up taking our jobs. This is the biggest issue with IT jobs! It's frustrating.

Worst thing I experienced in my 7 years of being a software engineer is when I have colleagues "being bored" over the weekend doing extra coding hours for work. Coding outside of work is of course fine, but do it on a personal project instead. This from my experience puts extra pressure on others who can't or don't want to do the same to deliver more etc. Love the video BTW, subbed.

I’ve never prepped for tech interviews, and all the work I’ve gotten was for companies who didn’t do a technical interview. For me, if a company requires a coding interview that’s an instant red-flag that they are behind the time, too much overhead, and just straight up don’t know what to look for in developers. I stay clear from those companies and I’ve always ended up in the most awesome, chill, low-stress environments with great management because of it. My advice is stop going for those 4-interview jobs… stop chasing the money so much. My work life balance is amazing because I avoid those and don’t solely seek high pay. Find smaller companies where you can talk with the owners, because those tend to be the least stressful and make this job amazing.

Thanks man. I just finished a coding challenge and it left me feeling low. This video has brought me back again to try again. It feels good to see the human side of this profession. I especially resonated with the "critical thinking all the time" it's really tiring. Once again....thank you 👊🏾

Wow thank you for this video! I work in big tech and it’s exhausting. After so many many years also the anxiety doesn’t go away, it certainly gets a bit better but you are constantly questioning yourself! I often feel guilty if I think about doing things outside of work and spend a few hours on something else apart from learning more about software or good design or learning more about the language I use and so on! I know it’s ridiculous but idk why we are all almost in the same boat. I think it’s high time we realize it’s a never ending treadmill we are on if we choose to stay in this industry!

I have been a Software Engineer for almost 15 years. The biggest piece of advice I can give to new devs is not to make a goal of working for a FANG or large company. The thing is I have worked for a large Tech company and know devs who are still working for some and you are just an employee there, just another cog in the wheel. Stick is the small to medium companies. You learn so much and do really cool stuff but you are also part of a smaller group that you don’t get lost in the crowd. Almost daily I can message the higher ups of the company and pick their brains about their company vision. I can shoot the shit with them as people not as these idols the media and tech industry makes them out to be. Picking this route you do miss out on 10-15k a year (USD) but you never run into burnout or the feeling of being lost in the crowd. You feel more like a family and the accomplishments never go unnoticed and under appreciated. Just my opinion. Great video and very nicely done!

I’m a computer science grad who is going to law school next month for cyber law. In the 9 months between my graduation and the start of law school, I’ve worked as a software engineer. And I have 100% realized that this is not for me. The burnout and constant push is for real. We never truly get a break, everything moves from one deadline to another. I never get that final feeling of completion. There is constantly more to do and less time to do it. Also, programming is super toxic. Not everyone, but a lot of software engineers have this mindset of “I need to work 12 hours a day, then go home and work on personal projects. I need to be coding constantly.” Programming isn’t even my true passion-I already knew that. But I still fall victim to the “no days off.” Even when I’m PTO or sick, I find myself tuning into sync meetings, doing work, getting chats from my teammates, etc. I cannot understand the people who do all of those things AND write 800 lines of code every weekend. A lot of people in CS get turned away from the field by how toxic it is. There is a lot of ego around software engineers-especially the silver spoon guys who had a great high school, a programming tutor, access to technology, learned programming young, etc. The most pissed I ever got at a coworker is when he said “if you don’t know C by high school you can’t be a software engineer.” I came into uni with no programming knowledge and had to spend a LOT of time learning and catching up. I was lucky enough to have some mentors and was able to do that. It pisses me off that this mindset of “you have to start super young” is taking hold, because a lot of very creative, intelligent people just don’t have those resources. The whole technical interview structure is garbage. The barrier for entry continues to climb higher and higher for no real reason. I think the industry is due for a massive shift. This simply isn’t sustainable. My advice to you all: I got totally burnt out on 9 months. It can happen fast. Don’t do what I did. Log off at 5 PM, don’t check Teams on your days off, work from home as much as possible, fuck the 40 hours / week structure, ignore your toxic teammates.

I’ve been a software engineer for a year now, the hardest part for me was getting my first position, learning stacks is hard but getting the first position was harder by far. I mustve sent out thousands of applications and it ended up taking about 8 or 9 months to get my first position. I went through at least a dozen interviews and maybe a 100 or so screenings. I would recommend spending your day 50% algorithms, 30% doing personal projects and the rest on applications. Get your projects expansive. Go full crud, include outside libraries like rxjs, material ui, become familiar with popular npm packages depending on your position and interests. And of course get a position in what your interested in! If you have Java, don’t take a Java position. If you hate front end? Don’t apply to a front end position, you’ll get burned out fast. I’m currently a front end dev with a larger company doing what I actually enjoy doing, my biggest headache with work is the amount of meetings goes into it. You have to meet with the UX team, the backend team, daily scrums etc etc. even as a junior half my day is meetings/mandatory training

Thanks for making this video, I have been struggling with imposter syndrome ever since I joined a FAANG company, I got to meet truly amazing engineers and wonderful folks, but it's inevitable to compare yourself to your colleagues. Truth is there will always be a lot of people, smarter, faster and more experienced than you, whatever you do. If you embrace many different hobbies and passions outside of work, you will always feel a bit behind, but that's okay. You can still bring your skills to the table, learn from them and do a great job, even if you are not in the Top 100 LeetCoders world wide. Be happy!

Software companies: "We don't have enough developers, why is that?!?!?!" Also software companies: "You have to have 3 years of experience and pass these 4 technical interviews to have a chance at applying for the Junior Software Engineer position"

As a senior in my final year of CS, I’d say I’m pretty burnt out at this point. I been programming since I was 11 years old and using computers at a high level since 08 and I’m just tired of the bureaucracy in the industry and in university . This “burnout” culture is unhealthy and inhumane as it stands. My passion has been extinguished (for now)

My experiences are quite similar, but I wanted to add some interesting things. First of all, when applying for a Junior position (meaning no experience at all), people expected someone having had years of experience somehow. It is quite unrealistic considering you probably just had your university graduation before or so. When I started off as a junior, people expected me to code. Now, after a few years, coding becomes less and less, but meetings, talking, and coordination as well as planning became the most important. I can be happy when I write a few hundred lines of code per day. Instead, I have to coordinate, to think about way different problems which have nothing to do with coding at all but with the processes of the software as well as the consequences for overall performance. And this is also something no one tells you. When being an architect, you don't build a house on your own, and the same goes for software engineering. You don't "build" much code on your own, but you have to understand the usage and consequences of code far more.

Thanks for the rant. I can relate to what you're saying. After about 15 years in the industry, I realised I wasn't strong enough to keep up the lifestyle and the imposter syndrome due to the perceived expectations. I cracked and quit my last two jobs. Not sure what I'm going to do next. I've been spending all my time to improve as a developer and really have little other marketable skills right now -- expect, maybe, the analysis of business requirements. Perhaps I should move into business analysis -- maybe there I'll be able to help make life easier for other developers by insisting on more reasonable expectations from business.

Critical thinking all day is super tough on the mind and body, you really have to remember and prioritize to taking care of yourself to not burn out

I think the reason why being in the tech industry causes anxiety or imposter syndrome is that the industry is so dynamic. The ever changing nature of it all makes people feel like they can't keep with everything, which you realistically can't do, but nonetheless it makes people feel overwhelmed and stressed thinking that they have to be up to date on everything new. Even though I don't have enough experience, my advice to people is keep using the knowledge you have and if there is a way to do what you already do more efficiently, learn it. Other than that, try to look at the new developments for fun, and if something from what you see interests you, learn it at your own pace. This is just my opinion though, other people may completely disagree but hey, I hope this helps.

As someone newly shifting into software development, I’ll say this, imposter syndrome will be probably the utmost biggest hurdle to overcome however once you overcome it, mentally you will be one refined individual in life.

I’ve been developing software for 13 years now. 100% agree with you on all the topics covered, including less hours in a work week for critical thinkers. It’s exhausting, but very rewarding. Thanks for sharing.

I've been writing code for nearly 38 years (27 professionally) and everything you're saying is spot on. I just can't do the Eat, Sleep, Code thing - never have. As much as I love coding I have other things I like doing as well. I'm 52 and also a father which also takes a lot of time from my day. As a result I've fallen WAY behind in the modern tech stack and finding new work with a good skill fit is incredibly difficult. I have ZERO regrets for the time I spend with my family and getting whatever "me" time I can. But my career depresses me - it shouldn't be this way, something needs to change in the industry. I know some people have suggested management. No, management is simply not for me. I just don't want the hassle of managing people - hiring, firing, discipline, politics, etc. I prefer the trenches.

I started out self-taught, it took 250 applications, 5 failed final stage interviews, and almost 2 years of continuous learning to get my first role. I could not find one thing in this video I disagree with, I experienced burnout and felt overwhelmed on numerous occasions. I still to this day sometimes feel like an imposter, even in spite of the many hours I spend upskilling. But in all honesty, it's a likelihood even the best of developers feel like this from time to time. The tech industry moves fast, very fast, and it's important to know becoming a developer is a continuous growing journey. What I would say, is if you're in it for the money alone, be conscious not to lead yourself to an unhappy place. I've known a number of people who entered the field with dollar signs in their eyes... collectively they all jumped ship within their first year. This all being said, if this is truly you're aspiration in life don't be disheartened by the difficulties of getting your foot in the door, you will get there with persistence, and if you're fortunate enough to work in the right place you will be supported. I can say with confidence if you're someone who welcomes continuous challenges, and creative problem-solving, in the right environment you will thrive. Imposters syndrome and burnout aside, never have I felt this fulfilled in my career, becoming a developer could be the best decision I ever made. I wish you all the best of luck.

I really appreciated this video. I'm beginning a journey to learn how to code and this popped up on my side bar. I don't think it was discouraging at all, personally. It's good to understand the full breadth of experience that I might be signing up for in pursuing this career, and these are things nobody else mentions within all the glam and hype of starting a career in tech. This gave me a lot to think about and some excellent warnings on what to look out for in myself, so that I can work towards establishing a sustainable lifestyle in this industry

Wow. I’m going through this right now. Pretty much having to do an intense 6 week Java course and expected to do an interview mock this week. Like I’m so exhausted trying to cram all this info in as I’m still relatively new to programming. I feel like I resonate with every single thing you’re saying without even technically being a programmer yet. I’ve not had a life for the past couple weeks

I've been developing software and data systems for 35 years, and you are spot on. I could have gone down the management path, but I love the work I do. There is one major aspect to having done this for so long - I can now tell people whether something is feasible or something is ridiculous, and they know I'm telling them the truth. I can also get away with telling higher-up where to go when they think I should be coding on my own time. I went the contractor route with my career. It's not for everyone, and you really have to stay organized in a lot of areas outside of what you do as a programmer, but done right, it affords you a lot of freedom. One of the reasons I only do contracts now is because I don't want to get tied to one company and possibly have to put up with people or a corporate culture that I may not like, for long periods of time. I agree with your assessments though, and I wish you much success.

Man, I have been in IT for over 20 years, what you mentioned is the absolute truth about job and the industry. I couldn't have summed it up any better than what you stated. Great video post!!

I went through a bootcamp and some how landed a junior role. No one really talks about how DIFFICULT interviews are and how HARD the the job can be. I definitely struggle daily to understand what I’m doing and how to do it. Tech isn’t that easy to pivot into from non-Tech back ground. It’s not impossible but some UKpostsrs and bootcamps really glamorize it but truth be told I’m not happy and feel extremely stressed out at work.

Thank you. Last year I completed my masters in Ed. Tech /Ed Design. I haven’t made the switch from being a HS Eng teacher into educational technology, but you’ve help put a lot of things into perspective for me.

I have been feeling a lot of burnout as a developer recently. I have been prepping for technical interviews and I have began to ask myself if this is even really what I want out of life. It feels like you have to sacrifice your mental health to continuously improve as a dev. Being glued to the screen and neglecting your life outside of that really adds up over time...

as a software developer, when you finish school, you really don’t ever stop learning. you spend a good amount of time outside of work learning the newest and greatest tech.

This video was exactly what I needed! I thought I was alone but you are 100% correct! The imposter syndrome and also coding outside of work! Thank you!!

I definitely am grateful for this because I did my bootcamp and im doing a bunch of algorithms and data structures now, but I have to get better at my resume. I get rejected all the time.

i'm over ten years into this and here's my advice: the quicker you can learn when to unplug, walk away, and let the problem settle so the answer can come to you the better off you're going to be. You need to learn a lot to make that possible but you gotta understand your brain tries to solve problems even after you stop... let it run the subroutines while you chill out with the wife or the boys.

I think this is a common problem for everyone and across all industries. Just figuring out how to live a fulfilled and balanced life enjoying all your interests and juggling multiple goals while maintaining a strong career.

I think part of what often gets overlooked is that you won't thrive in tech generally or software engineering more specifically if you're not the sort of person who thrives on always learning new things. Sometimes I get bored really easily if I'm not mentally focusing on something, which makes it difficult for me to ever completely shut down, but when you finally have a handle on a new concept, or learn to see something in a different way because you've learnt something new, there's no feeling quite like that satisfaction and I think that's part of the addiction for people like me and I assume you as well :) This doesn't just apply to my work but my life more generally as well.

Great video! I can confirm being a Computer Science grad from one of the most difficult CS programs in the country, burnout is very real, and can leave your mind in a very fragile state. Companies and or other organizations will _"utilize"_ your talents until they can't get it out of you the same way they used to and just terminate and have you replaced. Although that's also the harsh reality of the tech industry in general, even if you're a designer, programmer, or some business suit working at a tech company. Very, very unstable industry, but people need to remember there's a reason programmers typically make great salaries. Just because they may make great money for a little while doesn't mean they'll be happy.

I’m so happy someone finally said this!!! Breaking into the data analyst space was a complete nightmare for me. With my prior company, I applied to an associate and junior data analyst position multiple times for a product I was supporting for 6 years as the SME for the main module and most of the supporting modules. Preparing for those interviews was nothing short of a nightmare and my wife barely saw me for each of the 2 month long prep session I did to prepare!! I knew a few members of that team and asked them to help me prep each time and after every interview, I was crushed (both in the interview itself and from the result) as the things I prepped for were not asked in the interview and the technical question had nothing to do with the job. After two years of trying, I left the company and I am now a Sr. DA with another company where I got in on the first interview session. During the interview process, my director flat out told me that after work, he does not want me to do any tech anything (unless it is truly personal - like going back to school, etc.) and to spend time with my wife and rediscover or create a new hobby. After working for one of the largest SaaS and tech companies in the world, hearing a director from another incredibly large company say that was the main reason I joined. Happy to say I am happier than I have ever been now with the new company in the job I have been trying to get for nearly 3 years!! The tech world can be fun and the money can be great, but the mental and emotional cost is normally higher than most people realize or realize too late. Cheers for truth-ing, brother!

I’m a junior web developer for almost 2 years now. I still have to code after work just to get better at the new technologies we are implementing at work. It’s so hard to keep up with coding after work when you have to cook your own meals, want to hang out with friends and family and do cleaning chores. I’m at that point where I just would want to be a mid level developer, do coding for a few more years and look for another career path. Thanks for shinning a light on this topic.

great discussion on the downsides as you discussed. this could really be applied to any field but its good that you specifically spoke about it from the software engineer's perspective. i think it would help aspiring developers and other technologists to set better expectations for themselves by knowing what they want work/life balance to look like and always be evaluating if they are where they want to be at. comparing to other technologists is potentially misleading as everyone has different ideas of what success looks like. Equally important is for aspiring technologists to understand what is enough money for themselves and what does basic success look and feel like to them. Most of us just need to get working and we end up with unrealistic expectations and learn the hard way through burnout or worse by resigning ourselves to "this just isn't for me". Companies hiring don't know and don't necessarily care what your success model looks like even when they say they do. thanks for sharing this perspective.

Thanks for this posting and for your advice. I have been a QA engineer for 20 years (doing both manual and automation) and I very much enjoy what I do. I feel that to be successful in any field, you must have a passion for what you do. When I graduated from college in the mid 90's, jobs were very hard to come by. The Cold War had recently ended and so a lot of aerospace jobs in Southern California were being eliminated. However, I was able to take computer classes at a trade / tech school and at my local community college. I was very fortunate that I was able to find my passion in working with computers (even though I had already completed my degree in a different field). Later, when online learning platforms like Linda and Udemy were launched, I was able to take courses in database, programming and other software-related fields. Yes, I agree that software jobs can pay well but I feel it is more important to find your passion. If you love what you do, the money will come. Thanks Again.

I just recently retired after 47 years as a software engineer and this video is right on. It was not uncommon to work 110 hours a week when being paid for 40. (You are not considered to be a "team player" unless you work unpaid extra hours.) Schedule pressure is intense and never ending. You must also keep up with technology advancements on your own time which is very difficult. It also is not uncommon to finish a multi-year project and get leap frogged by technology. Like the video states, it is important to maintain relationships with those that are outside of the industry and to maintain outside interests. So what do I do now that I am retired? Yeah, I am still developing software and even a half century after writing my first program, I still enjoy it. The difference is that now I get to write things that I am interested in as opposed what someone else wants me to develop.

“The stress of critical thinking all the time”. Couldn’t have stated it better myself. That stress and mindset carries over into your normal life. I’ve solved many issues in bed not able to get work out my head and overthink things outside of work more than most!

I’m an Event manager with a major hotel brand. This video is important to me because one of my major issues with hospitality in general since COVID has been terrible staffing, overwork (13 hours a day) bad pay for the time and the burnout that comes with those. I am thinking to start learning the job and perhaps make a lateral move into Software Development. Honestly the money is the biggest part. I just started a family.

Excellent video and yes, it is a very difficult profession in these ways. This is why I get irritated when someone says something like "Oh, well, that's not really work because you do it for fun anyway." My answer is "Trust me, companies and customers find a way to make it into work." There's an argument that goes on as to whether programmers should code off the job and I think you've hit on why it doesn't get resolved. As someone who's been programming off and on in different ways since the 80s, I was never part of the race to get a FAANG job or its equivalent. I just wanted a programming job *somewhere*. During my first programming class in college, I was already coming up with ideas that I wanted to do through code and staying after school to use the computer lab simply because I loved coding. My perspective is that if someone truly has a passion for coding, they'll spend that time doing it because they want to and that's what creates excellence. The knowledge and experience come naturally as a result of that passion. Having said that, the culture that you described where developers punish themselves to this degree to get some some prized job with one of a few major companies is wrong. Promising developers are burning themselves out before they even start a job and I now see why people on the other side of the "code outside of work" argument get so angry when I talk about the necessity. Just the idea of 3 to 5 rounds of interviews is ridiculous and the excuse of not being a "culture fit" is a sign of a bad company culture in itself. I would say that the solution is for programmers to stop idolizing FAANG-type jobs and decide what their personal goals really are with software development. If you love the work and the tech, then find a way to keep loving it, even if it means settling for less money at a company that will treat you like a human. If you're just there for the money, you're probably going to be miserable no matter how much you're making and should do something else.

I've been writing code for 25 years. Self-taught, no CS degree. Just on-the-job learning. And I want to stress that it was ON-THE-JOB learning. The perception is that you have to do all this extra learning and reading outside of work. Some people do that and that's fine. But, it wasn't for me. I've been able to carve out a decent career without all that extra work outside the office. I also found that when you hear those people talking about all this new tech, they mostly only read a blog post and maybe typed a few commands they copy/pasted from that blog post. They aren't building production systems in their spare time. The valuable engineers I've ever worked with got things done at work and weren't distracted by all the new stuff they thought they needed to know.

Being a musician has the same pressures: people always expect you to be playing and practicing in your downtime like you have nothing else to do or a life to live.

Totally agree with you. I have come across many programmers in my time who code outside of office hours for fun. And there is that big problem of your skillset not being relevant anymore if you don't keep up with the new technologies, so you feel pressure to spend every waking hour learning new stuff. However, life is short and nothing can replace lost time with your wife and kids. My advice is be yourself and do something healthy outside of work. Life was meant for enjoying, not vegetating 24/7 in front of a screen.

This made me think a lot, thank you loads... I'm about to finish high school and i thought a lot about going for software engineering, but now I don't even know...I was always a bit more on introverted side and never really had life and this just seems like it's gonna take even more such as my own hobbies beside programming.

I think it comes from the reality that most people are in jobs without perks. Long hours and cant pay the bills. No time left for family and so forth. People that come from working minimum wage for years simply can't relate. Every disadvantage here exists in dead end jobs. The difference is you can't pay bills and your hungry wich is a whole other level of tired when you physically don't have the calories. This was me before I got into dev. If your reading and broke as a joe then trust me. You got this. It really is a game changer. The positives out weigh the negatives to the point there not even worth mentioning. That's why people don't talk about them. If you grew up cooking food in the oven with cardboard the disadvantages just don't exist.

This is all facts! Sometimes I can barely record after being on my computer all day doing homework. Love the content as always bro congrats on 100K 🍾 Keep grinding

Thank you for this video. I'm studying to go into cyber security right now while also staying open to other areas In tech and trying to decide where to go specifically. this helped me think about some of the baggage that comes with being a developer, narrow down my interests, and consider what life might be like working on the front of industry competition and mentally prepare for the pressure that also comes from peers.

Excellent video, so many truths! Thanks for making this video!

It’s definitely one of the toughest industries when it comes to interviews. Imagine a doctor walking into an interview and being asked a question he learned in his 7th year of college and then being asked to perform a minor surgery to fix it 😂 Edit: recently read a book on the life of a doctor and I now have a firm grasp on how difficult the phases before are and how much rejection you will face. The path to becoming a SWE is nowhere near as challenging but interviewing for the job still kind of remains the same. It can be crazy if it’s a top tier job.

For an intermediate developer going to advanced level ..i will say at first people really think its kinda easy to do programming but the bitter reality is that its not at all...mastering any craft takes alot of work, practice and endurance. programming need you to be mentally focused with just a goal in mind ..which is to get it done no matter what i faced...

I am a retired software engineer with more than 40 years experience. From my perspective, I think you are spot on. My biggest pet peeve is when bureaucracy gets in the way of technology. When a path forward is chosen because of politics and not for what is right. This happens way too much!

Great video. Thank you for touching on those subjects. The selection process for Big tech is brutal, but at the same time is a learning opportunity. You got to keep your head up and keep improving.

Pro-tip: Don't aspire to work in FAANG. Try other smaller companies where you will definitely be an asset and treated as such. Coding is a skill set that takes several hours and years to acquire and refine. Think about this, at most big companies, fortune 500 companies, you're basically killing yourself to land a role that pays the same as a smaller company. Also, in those big companies, some project manager or scrum master is going to have more job security and higher pay than you even though they offer less value to the company. "Leadership" roles are almost always perceived as more valuable to those types of organizations. Despite your high skill set and value they have found a way to put you in state of uncertainty and even fear. You're basically being pimped. You'll be like, "Of course I can take on a bigger load." You're the golden goose but they've got you constantly trying to prove your worth. They've got all of you vying to be the bottom bitch because they've created a system of scarcity through several rounds of interviewing tests and not hiring enough developers. So, by landing a role you feel a little bit special and you want to keep feeling that, "I'm special that's why I'm here and others aren't. I''m one of the ones that measured up." That's how they get you. "Of course I can do this big daddy, I'm one the best. That why you hired me big daddy, cuz I got what it takes. I got the skills daddy, ya dig!"

As someone that is getting ready to jump in head first into this field I applaud your brutal honesty. I have been through a coding boot camp and I feel like after completing this course I can tell you that the bootcamp was the reality check I needed to help me understand that this is the field I really want to be in. After working years of retail, I finally figured out to follow my passion in tech and pursue it no matter the difficulty. Although the difficulty was high, it never amounted to the stress I felt as a retail manager. I encourage anyone looking to better themselves in this field or another to go for it and understand that you are not stuck in your current role and there is always another opportunity out there...change is hard, you can do it.

My thing from the outside looking in, as someone whose only now looking down the barrel of a CompSci course and thinking of learning programming as an expansion to my skillset: I actually really want a job that expects me to use my brain more than my muscle, Having been in the Navy and mostly worked manual labor i'm just tired of mindless work that expects me to take item from here and put it there. (I'm also a little bit antisocial). So espite not understanding some of the terminology and not really having heard the gossip about salaries and benefits and everything, this was actually a pretty heartening video to watch. Thanks for the content.

i thought being a software engineer would be cool but it is very hard. Anyone can learn to code but its not for everybody. It is frustrating and time consuming. I found out the hard way. coding can be "fun" if you have the right mindset and personality. If you dont have those things it may not be for you and thats ok.

My biggest downside is my inability to quickly switch gears. For years each developer would build apps from ground up and they owned it. I knew my apps inside out and whenever a change was needed, I knew right where to go in the code and make the change. I could find the source of reported bugs quickly and fix them in minutes. Then we got new management and we had to implement agile development procedures where nobody owned anything and everyone works on everything. So now when I'm in the zone working on one app and I'm told I need to switch to a higher priority project to fix an issue, it takes me a while to get my bearings in this other app in order to do what needs to be done. Then switching back to the app I was previously working on isn't easy either. My brain is still in the other zone. Maybe now I'm just too old for this crap.

Speaking of interacting with people, I recently tried pair programming with a new guy at our company, and he and I both agreed that was the most productive 2 hours we've ever spent solving a problem. Human interaction when solving problems, is highly underrated in the software industry. The industry seems to be more focused on rewarding the cowboy programmer who sets off on his own, to conquer the world only with the arsenal in his holster. They forget that the tools that enabled such conquest were developed by GROUPS of like-minded individuals.

WOW!!! 4 years now, I have been looking for a job in the field and every thing you have said I personally feel is very true, I have had at least 1 interview every 6 - 8 weeks and the most common reason for not getting the job is "lack of experience" and like you say you go through the paper sifting, phone interview, face to face recruiter and then the final coding test, that is the answer. Personally think that fact that being 50+, a disabled guy in a wheelchair, no hair and no teeth, a little on the large size is not what an interviewer expects, and I don't fit the "stereo-type" programmer, and rather than be honest they give me the lack of experience but all I can do is keep studying, building my projects, and keep looking. So I really appreciate the time taken to do the video. I know that covid has had a massive affect on the industry. A recruiter once said that a company could have 1 candidate every day for an entire year and still not run out of candidates and I suppose there right.

Great video. Your honesty is refreshing.

Man i so appreciate when people like you admit to the over-glorification and ignoring the not-so-fun sides of being a software eng. In my current job, it isn't a software eng position, but it's at least half that, and I'm no expert, but yeah being able to Google and debug is so important. I know that there's a lot of value in the nitty gritty of data structures and algorithms, but some interviews are way over the top in terms of what they expect someone to know off the top of their head. I feel like that really only comes properly with experience, and it's hard to cram in otherwise. Thanks for opening up!

After having a rough round of interviews and ultimately getting rejected for a backend engineering position at company I was stoked on, this is what I really needed. Thanks so much for this.

i loved your video! thank you for all of the helpful information!

I am not an engineer but several of my friends are. Based on what I've inferred about their careers, and having worked for over 20 years in numerous environments, I love the way your content feels relevant to even people not even in IT. Your calm candor and the multiplicity of angles you offer makes for really rich contend my dude! Young professionals in any field can benefit from your raw honesty and vulnerability. Incidentally, you extinguished any FOMO I ever had about missing the opportunity to study computer science in college. My Philosophy degree feels like cozy cup of coffee.

Preach. Everything you said is exactly how I feel. I just finished a bootcamp and am working as a junior dev. I always feel like I need to do more and can never clock out at 5pm. Also my pay is significantly lower than what the media portrays so I spend good amount of hours everyday searching for new opportunities.

I think one of the problems is we all get a late start at software engineering. I’ve been “coding” for years but when I was starting it was fun side projects for years. Writing production code is different and we don’t start until first internship/first job. There’s this culture where at age 26 you’re supposed to be an expert when in reality you’ve just begun. This is what breeds the eat sleep code mentally bc there’s so much catch up that’s required to get to that level

I so feel the same, this is one of the most genuine videos I found on You tube. I beat myself a lot for not doing enough but the truth is I am already doing more than required!. I am grateful for all the opportunities I have currently but I am paying for those opportunities by sacrificing all of my hobbies outside coding. The sad reality of the IT industry!

Thank you, I appreciate this candid video. It has helped me on my path to figuring out what I want to do with my future.

Cool vid! Glad to find people out there I can relate with. However, we all would agree that the never ending deadlines and loads of work help us manage our time better in the long run, which I feel has been one of the most important skills as a developer, or any professional for that matter. Clocking out is imperative, we can't be at our toes 24x7, that's not efficient enough.

What I realized as a staff engineer (I don't believe in titles, but for context..) is the biggest stress comes from having too many things going on at one time. When you're an expert at the company, you're getting pings from 5 people a day, having 4 meetings a day to talk about different long term issues, plus working on 2+ coding projects at a time becomes way too much to keep in your head and the context switching is a huge mental stress. Pair that with being at a startup and it feels like if you don't do all these things, the company is going to suffer and your equity along with it. What's been really helping me is telling people "no, I can't talk, too many things going on" and generally trying to focus on one issue at a time, and understanding it's really not that big a deal if you don't solve all the problems all the time

Great video. A lot of these points actually sounded good to me so that helped me decide to be a programmer :)

It's so refreshing to hear from other software engineers that also have interests outside of coding. I went into programming because I actually enjoy coding, but I know that I would burn out really quickly if I didn't allow myself to have other hobbies once my workday is done. I feel so lucky that I'm finally at a point in my career where I can straight up tell recruiters I'm not interested in any jobs where I have to study for days for long coding challenges that have nothing to do with the actual job description.

Thank you for your video. I can certainly relate, being a computer engineer too. I feel working in tech does come with the fact that the industry is moving so fast, where people really can't keep up with everything that is going on. I read some of the comments below, and I'm glad to see that more experienced people are feeling this syndrome as well. I am over 40 and I am thinking of shifting my interest to software right now. This is why I reached your video, and I must say I was motivated to go into software engineering because of the benefits you've mentioned on the video. I think you;ve hit really great points, and gave me a good idea of what to expect on my journey. Thank you for that, and for the people in the comment section!

I relate to what you said at the end about the stresses of using critical thinking all the time, it's a huge part of burnout for me in the past. But I have come to the conclusion that if I wasn't critically thinking about my job as much I'd find other stressors to take it it's place which won't generate as much income or probably even reduce my effectiveness at work. Definitely a tricky balance and I'm sure I don't have it all figured out, but using my over actively critical mind to at least more income than I would in most other fields is very rewarding at the least.

This was very eye opening and sobering. I appreciate you.

The key is to know yourself and how your mind works. I’ve been in the industry for 20 years and I’m not burned out. I used to spend every waking hour studying coding practicing but I’ve learned that you can only do that for so long. Every so often just rest on your laurels and take a break from the study. Go workout and take photos and live your life then I guarantee you will be sitting on the toilet one day and you’ll get glued to a tutorial series about some random topic and you will be hooked by passion and not fear. Eventually learning will be second nature and you’ll do it naturally without getting exhausted.