Burnout is real – how to avoid it
61–70 of 128 posts
Re: Burnout is real – how to avoid it
#62> * You drag yourself to work and have trouble getting started
> * You’re irritable or impatient with co-workers, customers or clients
> * You lack the energy to be consistently productive
> * You find it hard to concentrate
> * You lack satisfaction from your achievements > * You feel disillusioned about your job
> * You use food, drugs or alcohol to feel better or to simply not feel
> * Your sleep habits have changed
> * You’re troubled by unexplained headaches, stomach or bowel problems, or other physical complaints
You say "burnout symptoms", Corporate says "reasons to fire you". Potato, potahto.
Re: Burnout is real – how to avoid it
#63Where and how specifically does Jira build in stress and burnout metrics and avoidance mechanisms into its tools and techniques? And when is it going to mandate a change of langauge in Scrum from "sprint" to some word vastly more reasonable in designating a staged, sustainable, work effort? The English language is in dire need of an idiom connoting the fox advising the henhouse. This post lacks all credibility.
Re: Burnout is real – how to avoid it
#64Re: Burnout is real – how to avoid it
#65Good compilation of the advice you often read about on the internet. However, a big factor in all of the solutions is having the support of the entire org/company. If your company doesn't believe that burnout is an issue and ignores your "no"s, gives you zero control over what is on your plate, and pressures you culturally, then to take back control, you are stuck fighting another battle on top of burnout. I've found…
It's even worse than this because, all of the factors you mention are actual risk factors for burnout (pressures, lack of control, isolation, fighting)
Re: Burnout is real – how to avoid it
#66Earlier quoted context omitted.
I've had both, and I don't know what is worst to tell you the truth. The ones who have coded a long time ago think that their experience in another language/ecosystem still allows them to estimate tasks in a completely different environment, when in fact it doesn't. The non-technical manager will focus more on the business side and will be easier to manage in many situations, but the problem is that that type fo mana…
I had a manager with a PhD who insisted on never writing multi-threaded applications because when he tried he failed and considered them dangerous. I routinely wrote apps using 10,000+ threads before. Now he is a head of development of some company. Real life is a comedy.
Re: Burnout is real – how to avoid it
#67Burnout is an inevitable consequence of the modern workplace for a lot of people. A lot of those who don't have any problem with burnout are the ones burning out other people. In the modern workplace, workers are often given a task without being given the good conditions to take it through, or a good overview of the context that the task is part of. A good percentage of the tasks but not all are hot potatoes, and it…
Totally, totally this.
To make an analogy, many companies seem to be run by a crazy crossfit overtainer dragging everyone else into workouts that are like the Bataan Death March.
Re: Burnout is real – how to avoid it
#68A pig In a cage On antibiotics
Re: Burnout is real – how to avoid it
#69Earlier quoted context omitted.
I had a manager with a PhD who insisted on never writing multi-threaded applications because when he tried he failed and considered them dangerous. I routinely wrote apps using 10,000+ threads before. Now he is a head of development of some company. Real life is a comedy.
Just create child processes with a shared memory region. That's not multi-threading.