News for hackers. Stuff that matters.
Re:How to spot symptoms of burnout on your engineering team by Brightwise on Friday April 14, 2017 @03:42AM (#14113172)
That's one of the worst articles on this topic I've ever read.
Re:How to spot symptoms of burnout on your engineering team by YCode on Friday April 14, 2017 @10:39AM (#14114702)
Could anyone recommend a better one?

No sarcasm intended, this is an important issue.

Re:How to spot symptoms of burnout on your engineering team by Brightwise on Friday April 14, 2017 @02:18PM (#14116058)
If we want to approach a topic "How to detect/avoid B/o" in a scientific manner, we should begin with a definition of what that condition is and what it is caused by.

It's been some years since I investigated on that topic, but I remember there are basically two paradigms:

A) Blame the guy/dev/employee B) Blame the company/environment/manager

Depending on your point of view, you may want to settle somewhere in between these two extremes. I find "The truth about burnout" by Maslach/Leiter in my bookshelf, who where the first ones doing a proper scientific analysis. They pretty much end up with paradigm B. As a dev, I liked that.

Re:How to spot symptoms of burnout on your engineering team by YCode on Saturday April 15, 2017 @01:38AM (#14119553)
Thanks I'll have to check that out.

I suppose I'd go with B, though I have no idea what to do about that.

Re:How to spot symptoms of burnout on your engineering team by heisenbit on Friday April 14, 2017 @06:40AM (#14113655)
I was thinking this is a very important and worthwhile topic. But the article reads like bullet points dreamed up in one minute and then filled up with sweet cotton.
Re:How to spot symptoms of burnout on your engineering team by pasta on Friday April 14, 2017 @03:59AM (#14113215)
It's an ad for (bad) managers.
Re:How to spot symptoms of burnout on your engineering team by sauronlord on Friday April 14, 2017 @03:47AM (#14113183)
Glad someone said it.