It took me a long time to realize that yes the Programmer's job is stressful, really stressful! We just don't recognize it as the pressures start out slow and then mount up. What works the best for me now, (but I've been at this for 25+) years, is to just take the medicine.
Just Take The Medicine?
There are different personality types, some are amenable, some antagonistic, and the entire spectrum in between. I try as hard a possible to just let the personality type fly by me (everyone has a backstory and dysfunctional past). This brings me to focus on what they want and to embrace their system of measuring it.
The kahunas in the sky (including Project Managers, Scrum leaders, and People Managers) all have pressures too. In fact the 1st line people managers have it the worst. They are squeezed somewhere in between expenditures and deliveries. They have to sit in on monthly, quarterly meetings to justify expenditure. A wonder position when deliveries are meeting/exceeding expectation, a terrible position when corrective action is needed. Just remember, the world is controlled by accountants. They pay us, the pay bills, they watch the shop and keep businesses going.
Don't fight backt
It's ok to voice comments but we should not be dogmatic and unpleasant, we should not drag people through our nightmares. No matter how true our perspectives are, we have to leave plenty of room for their passages to accomplish what they feel is the right way, even if we can see the writing on the wall.
Writing on the Wall?
Important projects take on a life of their own. In today's Agile, ScrumMaster world, the primary focus is delivery. If the daily meetings are done correctly, then impediments are identified usually within a week. However, if the impediments are not addressed by upper management like (we don't need more CPU power, more bandwidth, shoot we don't even need our own network people in on this). Then the writing is on the wall. What this means is that this particular part of the project is in a slow death spiral. The tendency of the organization is to place all responsibility on the developer. As good developers the best thing we can do is take full responsibility except where we have no control. We have to try to do uncomfortable things like make unauthorized contacts to other departments, (you know with the people too busy with other things). And then just report all our activities each day.
Bottom line is that due to the lack of focus on the impediments you as a developer will eventually have a bad mark in some upper people's minds! It's all dependent on how favorable you are presented by other's like the scrum master, the team lead, the managers etc. The problem is did they ever get the real story? Are they really vested in this?
If the answers are no, then you need to find another job, or just wait until they take you out. There's always better jobs to be found. Don't worry, be happy for the experience (even the bad ones)
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.
It took me a long time to realize that yes the Programmer's job is stressful, really stressful! We just don't recognize it as the pressures start out slow and then mount up. What works the best for me now, (but I've been at this for 25+) years, is to just take the medicine.
Just Take The Medicine?
There are different personality types, some are amenable, some antagonistic, and the entire spectrum in between. I try as hard a possible to just let the personality type fly by me (everyone has a backstory and dysfunctional past). This brings me to focus on what they want and to embrace their system of measuring it.
The kahunas in the sky (including Project Managers, Scrum leaders, and People Managers) all have pressures too. In fact the 1st line people managers have it the worst. They are squeezed somewhere in between expenditures and deliveries. They have to sit in on monthly, quarterly meetings to justify expenditure. A wonder position when deliveries are meeting/exceeding expectation, a terrible position when corrective action is needed. Just remember, the world is controlled by accountants. They pay us, the pay bills, they watch the shop and keep businesses going.
Don't fight backt
It's ok to voice comments but we should not be dogmatic and unpleasant, we should not drag people through our nightmares. No matter how true our perspectives are, we have to leave plenty of room for their passages to accomplish what they feel is the right way, even if we can see the writing on the wall.
Writing on the Wall?
Important projects take on a life of their own. In today's Agile, ScrumMaster world, the primary focus is delivery. If the daily meetings are done correctly, then impediments are identified usually within a week. However, if the impediments are not addressed by upper management like (we don't need more CPU power, more bandwidth, shoot we don't even need our own network people in on this). Then the writing is on the wall. What this means is that this particular part of the project is in a slow death spiral. The tendency of the organization is to place all responsibility on the developer. As good developers the best thing we can do is take full responsibility except where we have no control. We have to try to do uncomfortable things like make unauthorized contacts to other departments, (you know with the people too busy with other things). And then just report all our activities each day.
Bottom line is that due to the lack of focus on the impediments you as a developer will eventually have a bad mark in some upper people's minds! It's all dependent on how favorable you are presented by other's like the scrum master, the team lead, the managers etc. The problem is did they ever get the real story? Are they really vested in this?
If the answers are no, then you need to find another job, or just wait until they take you out. There's always better jobs to be found. Don't worry, be happy for the experience (even the bad ones)