Burnout is real – how to avoid it
31–40 of 128 posts
Re: Burnout is real – how to avoid it
#32>Quick...tells his students he’s always available – except between 10pm and 6am. It’s important to put limits on when you’re reachable, he says. Really...this is their example of healthy boundary setting? A professor who says he's available the entire time he's awake, but won't answer emails when he's supposed to be sleeping.
Average healthy sleep time is 8 hour a day. Even if it's less for some, this professor can be disturbed when he eats ? When he is in his shower ?
Seems strange to me.
Re: Burnout is real – how to avoid it
#33Earlier quoted context omitted.
That is literally the definition of the word. If you can run for more than, at most, a minute or so at a given pace you are pr. definition not sprinting.
Isn't any running unsustainable though ?
Re: Burnout is real – how to avoid it
#34Earlier quoted context omitted.
That is literally the definition of the word. If you can run for more than, at most, a minute or so at a given pace you are pr. definition not sprinting.
Isn't any running unsustainable though ?
Re: Burnout is real – how to avoid it
#35>Quick...tells his students he’s always available – except between 10pm and 6am. It’s important to put limits on when you’re reachable, he says. Really...this is their example of healthy boundary setting? A professor who says he's available the entire time he's awake, but won't answer emails when he's supposed to be sleeping.
Re: Burnout is real – how to avoid it
#36What is funny about this is that Atlasssian’s Jira product is designed for two week “sprints”, a term referring to the idea of running quickly at a rate above a sustainable pace with no intent to keep running after the end. But these sprints normally are done repeatedly with no actual stop or sight of a finish line. Employees just churn through tickets with no designed breathing room or planned downtime. Jira is prob…
In JIRA your performance is constantly measured comparing the actual work against the estimates, which are usually not under the developer control. There are reports produced that developers don't get to see that the manager does to compare developers this way. Of course, this can be easilly gamed. The most cunning developers will go out of their way to get the tasks that are clearly defined in scope and that they ar…
We use JIRA and we find it extremely useful, although we never use real-time values for estimates or reporting. Story points, which I believe are recommended by the Agile framework, are used to estimate and draw burn down charts and reports. We can then use these to adjust our estimates for future sprints.
JIRA really is a tool and just because some managers use it poorly, doesn't mean that is why it was created. Those managers would be bad regardless of the tool.
Re: Burnout is real – how to avoid it
#37Earlier quoted context omitted.
> “sprints”, a term referring to the idea of running quickly at a rate above a sustainable pace why would it it be "above sustainable pace".
That is literally the definition of the word. If you can run for more than, at most, a minute or so at a given pace you are pr. definition not sprinting.
Re: Burnout is real – how to avoid it
#38Earlier quoted context omitted.
That is literally the definition of the word. If you can run for more than, at most, a minute or so at a given pace you are pr. definition not sprinting.
Sprints also have a specific meaning in Agile/Scrum vocabulary which should be pretty common around here. That's like suggesting github promotes physically aggressive behavior because it's centered around pushing. Nothing about a sprint in Scrum terminology is meant mean an unsustainable pace.
Humpty Dumpty smiled contemptuously. 'Of course you don't — till I tell you. I meant "there's a nice knock-down argument for you!"'
'But "glory" doesn't mean "a nice knock-down argument",' Alice objected.
'When I use a word,' Humpty Dumpty said, in rather a scornful tone, 'it means just what I choose it to mean — neither more nor less.'
-- L. Carroll
Re: Burnout is real – how to avoid it
#39Burnout 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…
> a clueless middle manager who has never coded the simplest of programs in his/her life. I've never had manager who hasn't coded ever in his life. WhatI had most of the time was a manager who hasn't coded in a longtime.
Putt's Corollary: "Every technical hierarchy, in time, develops a competence inversion." with incompetence being "flushed out of the lower levels" of a technocratic hierarchy, ensuring that technically competent people remain directly in charge of the actual technology while those without technical competence move into management.
https://en.wikipedia.org/wiki/Putt%27s_Law_and_the_Successfu...
Re: Burnout is real – how to avoid it
#40Burnout 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…
I've worked in the industry for 10 years and have never seen any of this, except for three people who were PIPd.