3

do you guys have stories about burnout or boreout?

Comments
  • 1
    I think, in essence, all such stories will sound the same.
  • 1
    @Vross i guess, but i'd like to hear if they got out and how
  • 5
    Daily: App A is crashing on some place, because I know the codebase is shit, I go out of my office and tell my guys to cover my calls while I go get us coffee, lead dev asks about the crash, I tell him not to worry that I will take care of it while he continues his support for other items, dude has lots on his plate already, so do I, but lead by example eh? Walk the longest route possible to make it to the caffeteria, which is two buildings down from the I.T building. Go into the cafeteria, chit chat with the people there, go get the coffee, slowly walk back, give me lads their black brews (5 creamers on the side for each, splenda for some, regular sugar for the others, they mix it to their heart's content)

    Walk into my desk, open the application repos. Ah, the wonders of intellisense, I have found the error in roughly 2 minutes, but the whole ordeal to prepare for it was about 30 mins. Drink coffee, sit there trying to will the power to finish it cuz I am tired.

    Rinse, repeat.
  • 3
  • 2
    Burnout is when you survive a 6 month project that takes 18 months,
    Then jump into another on the back of that and deal with more incompetent consultants then anyone ever should and plus train multiple new staff and fill the knowledge gap void created by recent departures.

    Burnout is having 20 odd projects under your fingers (monolithic to micro) in different languages and hosted in different environments and you being the only dev that knows how most of them work.

    Burnout is when... nope, burnout is right fucking now for me 🙃

    Bore out on the other hand is when you've been burnt to the ground and can't muster the will to give a shit anymore and just sit their with your head in your hands wanting something to break just so you can do something of practical use.

    🤦‍♂️ welp, that felt good getting that off my chest, now to start a Wednesday.
  • 2
    For me burnout happened pretty quick. At least I think it was but it could have been stress or a virus attacking my brain. I never got answers.

    Over a few weeks my ability to concentrate deteriated until I was just utterly confused while working. Some people refer to this as a fuzzy head like you can get with Lyme disease. I once spent a whole day copy pasting files between projects. I started to experience depersonalisation where I felt under water or similar and I felt disconnected to my body, I felt like my body was a puppet and I was looking through holes in a wall, or like a vr headset. I got sensitive to light, especially the lights in the office and I was constantly squinting to see, at some point just crossing the street was very difficult and stressful.

    It took me close to 1 year to see improvement, another year to get close to normal, another year to get back to what I believe is normal.

    If that is burnout then I don't wish it on anyone. I hated every second of my life.
  • 2
    1.5 million lines of undocumented, untested spaghetti code job. Almost 2 years.

    I stopped working for roughly a year and a half, took a break, studied, stopped programming altogether, traveled a bit. If you can afford to do it, i strongly encourage people to take a long break from it.
  • 1
    I single handedly saved the agency I was working for from going out of business. I pulled some long hours, and worked weekends. Closed some big work orders, got praise from the bosses etc…

    My efforts were totally squandered, mostly on terrible hires, and they ended up going out of business after 7 months anyway.

    I was already burnt out heading into the next job. I realized the new team was in a sorry state of affairs, and I just hit the eject button.

    I went to hike the AT, it was awesome
Add Comment