“Toxic” is just a label you’re putting on everything you don’t like and you’re also putting a ton of implications behind it.
If Stacy wants a feature, and she’s the official representative, I need to clarify what that feature means. A manager can’t shield me from having to research the technical implications, that’s my job.
Also, you can ignore calls all you want, if there is a genuine need to communicate, you need to have that call at some point. That’s actually your first point in the list above.
I think you never worked in a role above code grunt. As a senior developer, my job is to do all what I described above. I need to do all the technical legwork a manager can’t. I need to write everything down. I need to get feedback from stakeholders. That’s nothing a manager can do and that’s nothing a junior can do.
It’s not a label im making up. Toxic here is a synonym for unhealthy. If someone keeps calling you, interrupting you, micromanaging you, disrespecting your working hours or your focus times, that’s an unhealthy relationship.
Stacy is entitled to regular details, sure. That’s why we have tickets, and daylies and retros. She’s not entitled to asking multiple times day if you’re done yet.
I work above senior, have done management and tech lead. I’ve seen toxic workplaces, and I’ve seen good ones. I recognize the need for all the agile rituals. But that still doesn’t entitle people to call all the time and interrupt you.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Nah, I think you’re mixing things up here.
“Toxic” is just a label you’re putting on everything you don’t like and you’re also putting a ton of implications behind it.
If Stacy wants a feature, and she’s the official representative, I need to clarify what that feature means. A manager can’t shield me from having to research the technical implications, that’s my job.
Also, you can ignore calls all you want, if there is a genuine need to communicate, you need to have that call at some point. That’s actually your first point in the list above.
I think you never worked in a role above code grunt. As a senior developer, my job is to do all what I described above. I need to do all the technical legwork a manager can’t. I need to write everything down. I need to get feedback from stakeholders. That’s nothing a manager can do and that’s nothing a junior can do.
I code something like half an hour a day.
It’s not a label im making up. Toxic here is a synonym for unhealthy. If someone keeps calling you, interrupting you, micromanaging you, disrespecting your working hours or your focus times, that’s an unhealthy relationship.
Stacy is entitled to regular details, sure. That’s why we have tickets, and daylies and retros. She’s not entitled to asking multiple times day if you’re done yet.
I work above senior, have done management and tech lead. I’ve seen toxic workplaces, and I’ve seen good ones. I recognize the need for all the agile rituals. But that still doesn’t entitle people to call all the time and interrupt you.
None of the things you mentioned were in my description. You made that up completely. I talked about meetings, no scheduling information.
Did I even imply that? No. You made that up.
Hearing only what you want, not what the other person said makes you almost perfect management material.
Seriously, look at my comments and your replies. You answered to a completely different reality.
I might… Have mixed multiple thread. I’m sorry