I've found that any project that exceeds 6 months in length tends to drag everyone down mentally. Past that point, the project starts to feel like it just drags on and on. There's usually no option but to press on and push it to completion because anything else is a distraction. Of course, after a lengthy project has completed, taking a long break is absolutely necessary. Since everyone burns out at different rates, there's probably no easy formula for calculating how much time off any one person needs to recover. Also, the workload over a team is likely to be unevenly divided as well.
It is always a good idea to re-evaluate scope creep potential from time to time. If something can be cut from the project and set aside for later development that shaves off a month or two of dev work, then dropping it might be disappointing but gets the project out the door sooner rather than never. The longer a project takes, the more likely it is that it will fail to ever reach completion.
It would be far easier to self-identify burnout and bring it to the attention of others if mental health was deemed as important as "the bottom line" (i.e. profits). That's not how today's society is structured though as people are largely tools to maximize profits above all else. It's an unfortunate reality of the world we live in.
Burnout happens a lot faster on projects where there's no vested personal interest in the project. That is, the developer doesn't believe the project has value or it doesn't align with their own personal goals.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've found that any project that exceeds 6 months in length tends to drag everyone down mentally. Past that point, the project starts to feel like it just drags on and on. There's usually no option but to press on and push it to completion because anything else is a distraction. Of course, after a lengthy project has completed, taking a long break is absolutely necessary. Since everyone burns out at different rates, there's probably no easy formula for calculating how much time off any one person needs to recover. Also, the workload over a team is likely to be unevenly divided as well.
It is always a good idea to re-evaluate scope creep potential from time to time. If something can be cut from the project and set aside for later development that shaves off a month or two of dev work, then dropping it might be disappointing but gets the project out the door sooner rather than never. The longer a project takes, the more likely it is that it will fail to ever reach completion.
It would be far easier to self-identify burnout and bring it to the attention of others if mental health was deemed as important as "the bottom line" (i.e. profits). That's not how today's society is structured though as people are largely tools to maximize profits above all else. It's an unfortunate reality of the world we live in.
Burnout happens a lot faster on projects where there's no vested personal interest in the project. That is, the developer doesn't believe the project has value or it doesn't align with their own personal goals.