News for hackers. Stuff that matters.
Re:Burnout from an Organizational Perspective by danielheath on Saturday June 12, 2021 @07:09PM (#27488203)
IMO burnout comes from failing to ship something worthwhile; the feeling that “despite how hard you worked, it didn’t matter in the end” is at the core of my experience with it.

You find yourself thinking “I was sure that would be good and worked hard, and it turned out not to be. Now I am sure my new project will be good, but how can I know it’s going to go differently”.

Re:Burnout from an Organizational Perspective by nerdponx on Saturday June 12, 2021 @07:15PM (#27488246)
I've been here myself, and I've seen it in others.

Having too much responsibility to early in one's career I think is a significant risk factor, especially combined with certain personality types. Moreso if you lack a strong professional network and/or mentorship. This situation is often correlated with clueless and/or ineffective and/or hostile management, which is it self an exacerbating factor.

I don't think it's the only cause, but it's probably a common one.

Re:Burnout from an Organizational Perspective by toast0 on Sunday June 13, 2021 @03:04AM (#27490449)
I think you get to burnout pretty quivk with overwork and no worthwhile ouput, but you can also get there with overwork and good output over a long enough period, too.
Re:Burnout from an Organizational Perspective by danielheath on Sunday June 13, 2021 @07:38PM (#27497669)
It’s not enough for the output to be good; you have to feel like it was worthwhile.

Building and shipping great software that goes on to have few or no users? Burnout.

Building widely used software but you come to believe it does more harm than good? Also burnout.

Avoiding it requires believing in the value of the things you have done; imo overwork can only speed up the process, but will not cause it if you believe in the rightness of what you are doing.