Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "#jobs #burnout"
-
Today I realized that I hit a total burnout. Last 3 years were extremely stressful for me (4 jobs in 3 different countries, exhausting and toxic relationship, bad habits). Last 7 months are the worst. I became lonely isolated and miserable. I learned to rely purely on stress, determination and validation to get through my days. Was supressing my emotions for a long time just to focus on making the money. Its time to break the cycle.
Im done with this. Next week Im quitting my fulltime job. Saved enough money for starting capital of my own dev services company. Built three projects that generate stable income to cover my living costs. Now finally I can take a long break to recover from this burnout and to heal myself. That poor persons mentality that I had from my poor family has been shattered. I achieved what I wanted in terms of having the money and gathered enough experience necessary to survive anywhere.
I managed to get through all this shit on my own with barely any support. People around me were draining me more than actually helping me. But I managed to do it and now its time to focus on myself, to heal and restore love for living. Im safe now.10 -
[long]
When searching for internship via school I found this small startup with this cute project of building a teaching tool for programming. There were back then 2 programmers: the founder and the co-founder.
Then like 1 week before the internship started, the co-founder had a burnout and had to get off the project, while the company was so low on budget the founder, aka my new b0ss, had to work separate jobs to keep the company alive. (quite metal tbh)
It's funny because I'm a junior developer, 100%. I've been coding as a hobby for around 8 years now but I've never worked in a big company before. (No exception to this workplace either)
First project I get: rewrite the compiler. The Python compiler.
"But wait, why not just embed a real compiler from the first case?"
-nanananana it's never simple, as you probably know from your own projects.
The new compiler, as compared to existing embedded compiler solutions out there, needed these prime features:
- Walk through the code (debugger style), but programmatically.
- Show custom exceptions (ex: "A colon is needed at the end of an if-statement" instead of "Syntax error line 3")
- Have a "Did-you-mean this variable?" error for usage of unassigned variables.
- Be able to be embedded in Unity's WebGL build target
All for the use case of being a friendly compiler.
The last dash in the list is actually the biggest bottleneck which excluded all existing open-source projects (i could find). Compliant with WebAssembly I can't use threads among other things, IL2CPP has lots of restrictions, Unity has some as well...
Oh and it should of course be built using test-driven development.
"Good luck!" - said the founder, first day of work as she then traveled to USA for **3 weeks**, leaving me solo with the to-be-made codebase and humongous list of requirements.
---
I just finished the 6th week of internship, boss has been at "HQ" for 3 weeks now, and I just hit the biggest milestone yet for this project.
Yes I've been succeeding! This project has gone so well, and I'm surprising myself how much code I've been pumping out during these weeks.
I'm up now at almost 40'000 lines of source and 30'000 lines of code. ‼
( Biggest project I've ever worked on previously was at 8'000 lines of code )
The milestone (that I finished today) was for loops! As been trying to showcase in the GIF.
---
It's such a giant project and I can honestly say I've done some good work here. Self-five. Over-performing is a thing.
The things that makes me shiver though is that most that use this application will never know the intricates of it's insides, and the brain work put into it.
The project is probably over-engineered. A lot. Having a home-made compiler gives us a lot of flexibility for our product as we're trying to make more of a "pedagogic IDE". But no matter that I reinvented the wheel for the 105Gth time, it's still the most fun I've had with a project to date.
---
Also btw if anyone wants to see source code, please give me good reasons as I'm actively trying to convince my boss to make the compiler open-source.
Cheers!4 -
The past couple of days have been, like:
- I can’t focus on my side project
- I can’t bring myself to study for the AWS certification exam I’m taking next week
- I haven’t had the will to do a single code challenge
- It’s hard to write cover letters for jobs when no one has responded to a single job application I’ve done in the past couple of weeks
- Even doing things that traditionally give me joy ... bring me no joy.
Is this what burnout feels like?9 -
After reaching the pinnacle of my latent burnout and mental overload lately I quit and managed to get paid leave for the rest of the notice period through hr as I told them I'm not able to work for them anymore and else had to go on sick leave. My brain just had to have a clean cut and blocked me from
getting into their overcomplex and shitty, unplanned projects as I see no value in doing anything for them anymore. I gave them all my access keys and a small handover, but it was clear that they would run into problems without me, cause I've been doing like 5 jobs there due to developer shortage. Now I still get requests from my manager even though I had an operation and spent last week in the hospital and am still recovering for the next two weeks. He's still trying to build pressure as if it was my fault that we never got time to document stuff properly and automate things that have to be automated. He ignored every recommendation I made in past to ensure that things keep running when I leave, as I always knew that I wouldn't do this shit for long. It was always more important to please bosses ever-changing requests and stupid whims as fast as possible at the cost of quality, pressuring us into putting projects live at 80% to meet random deadlines we had no say on. What a fucking asshole trying to put the responsibility on me now. Not my problem anymore. Have fun finding someone else taking over that shithole of an underengineered software-architecture. I'm out!1 -
1) Never be afraid to ask questions.
There are so many instances of situations where assumptions have been made that shouldn’t have been made, resulting in an oversight that could have been rectified earlier in a process and wasn’t.
Just because no one’s asking a question doesn’t mean you’re the only person who has it.
That being said, it’s really important to figure out how to ask questions. Provide enough context so that the audience for your question understands what you’re really asking. If you’re trying to troubleshoot a problem, list out the steps you’ve already tested and what those outcomes were.
2) When you’ve learned something, try to write about it. Try to break it down as though you were explaining it to a child. It’s through breaking down a concept into its most simple terms that you really know that you understand it.
3) Don’t feel like you have to code *all of the time*. Just because this is what you’re doing for a living doesn’t mean that you have to make it your life. Burnout is real, and it happens a lot faster if it’s all you do.
4) Find hobbies outside of tech!
5) Network. There are a number of great communities. I volunteer for and am a member of Virtual Coffee, and can vouch for that community being particularly friendly and approachable.
6) Don’t let a company pay you less than industry standard and convince you that they’re doing you the favor of employing you.
7) Negotiate salary. Always.
8) If you’re a career transitioner, don’t be afraid to talk about your previous work and how it gave you experience that you can use in programming. There’s a whole lot of jobs that require time management, multi-tasking, critical thinking, etc. Those skills are relevant no matter where you got them.
9) If it takes a while for you to get a gig, it’s not necessarily a reflection on you or your abilities.
10) Despite what some people would say, coding’s not for everyone. Don’t feel like you have to continue down a road just because you started walking down it. Life’s not a straight path. -
The year was 2006. During the first half of my career, I use to work in the NOC. This was before I made my transition to software engineer. I worked on the third shift for a bank services company. The company was on a down turn. Just years earlier they just went public, and secured a deal with a huge well known bank. Eventually they entered a really bad contract with the bank and was put into a deal they couldn't deliver on. The partnership collapse and their stock plummeted. The CEO was dismissed, and a new CEO came in who wanted to "clean things up".
Anyway I entered the company about a year after this whole thing went down. The NOC was a good stepping stone for my career. They let me work as many hours as I liked. And I took advantage of it, clocking in 80 hours a week on average. They gave me the nick name "Iron Man".
Things started to turn around for the company when we were able to secure a support contract with a huge bank in the Alabama area. As the NOC we were told to handle the migration and facilitate the onboarding.
The onboarding was a mess with terrible instructions that didn't work. A bunch of software packages that crashed. And the network engineers were tips off, as they tunnel between our network and the banks was too narrow, creating an unstable connection between us and them. Oh, and there were all sorts of database corruption issues.
There was also another bank that was using an old version of our software. The sells team had been trying to get them off our old software for over a year. They refuse to move. This bank was the last one using this version, and our organization wanted to completely cut support.
One of the issue we would have is that they had an overnight batch job that had an ETA to be done by 7 AM. The job would often get stuck because this version of the software didn't know how to fail when it was caught in an undesired state. So the job hung, and since the job didn't have logging, no one could tell if it failed unless the logs stopped moving for an hour. It was a heavily manually process that was annoying to deal with. So we would kill the JVM to "speed" the job up. One day I killed the JVM but the job was still late. They told me that they appreciated the effort, but that my job was only to report the problem and not fix it.
This got me caught up in a major scandal. Basically they wanted the job to always have issues everyday. Since this was critical for them, all we needed to do was keep reporting it, and then eventually this would cause the client to have to upgrade to our new software. It was our sales team trying to play dirty. It immediately made me a menace in the company.
For the next 6 months I was constantly harassed and bullied by management. My work was nitpicked. They asked me to come into work nearly everyday, and there was a point I worked 7 days with no off days. They were trying to run me so dry that I would quit. But I never did.
On my last day at the company, I was on a critical call with a customer, and my supervisor was also on the line. My supervisor made a request that made no sense, and was impossible. I told her it wasn't possible. She then scalded me on the call in front of customers. She said "I'm your supervisor, you're just a NOC technician, you do what I say and don't talk back". It was embarrassing to be reprimanded on a call with customers. I never quite recovered from that. I could fill myself steaming with anger. It was one of the first times in my adult life that I felt I really wanted to be violent towards someone. It was such a negative feeling I quit that day at the end of my shift with no job lined up.
I walked away from the job feeling very uncertain about my future, but VERY relieved. I paid the price, basically unable to find a job until a year and a half later. And even was forced to move back in with my mother. After I left, the company still gave my a severance. Probably because of the supervisor's unprofessional conduct in front of customers, and the company probably needed to save face. The 2008 crash kept me out of work until 2009. It did give me time to work on myself, and I swore to never let a job stress me out to that degree. That job was also my last NOC job and the last job where did shift work. My next few jobs was Application Support and I eventually moved into development full time, which is what I always wanted to do.
Anyway sorry if it's a bit long, but that's my burnout story. -
I think it's about time I leave my current role for a new one. There is a lot that I can still learn here, however, I feel as though I am no longer in control of my career. The days just drone on as new tickets populate my to do list.3
-
I think I am going through burnout.
How do I deal with it?
Joined a startup with crazy work culture in Jan.
Have been working 14 hours a day for months starting march 2020, and even that was only to barely keep up with my colleagues. I have been one of the top performer in my previous jobs.
since the beginning, It always bothered me seeing people working on weekends, and falling behind if I didnt, to not have time for anything else, but I started really hating it a couple of months back.
Work has slowed down a bit now, but I just can't do it. Cant focus and get even basic tasks done. Still getting by with last minute efforts but I hate it!
Dont have the guts to leave the job, but also realise I am not doing enough and will get kicked out eventually anyway.
What can I do, to get over this?15 -
now... Im just tired and bored of what i do. i had a very hectic year rewriting a core functionality in my company, it was full of optimizations, logic improvements and learning new things.
I took 10 days off hoping id come hating my job less. I learned kotlin and worked on a personal server side project with it during the vacation and honestly i loved it. I missed learning new languages and concepts.
so i thought, well if i enjoyed coding during the vacation then my burnout is cured right ? well once i went back to work today I felt like shit and couldn't do a thing. disgusted of the idea coding for my employer. Too tired to continue my personal project after 8 hours of my job
I guess im back to square one2