Earlier quoted context omitted.
I literally don't know how else to deal with certain categories of folks with whom talking and trying to resolve the issue has no effect. Going around them/ignoring them is literally the advice you get from basically every literature I've read, and I've read a lot about this. But you do have to try to work through the issue first, and you have to be willing to try again if they seem open to resolving the problem down…
What would you suggest from your readings? I've mostly benefited from hard realism approach and Actor theory (as applied by some: everyone has an agenda, to work with them: Align, make Peace, or Destroy).
How to deal with difficult people on software projects
61–70 of 130 posts
Re: How to deal with difficult people on software projects
#62This is a horrible website and you will likely experience diminished tenure if you follow it's advice. First, there is a complete lack of empathy for the person being labelled. What are the motivations and constraints that led to this person acting this way? A key question and the foundation for building healthy productive relationships. Second, the 'solutions' are horrible. "Go around the person" is terrible advice…
Fully agreed. Amusingly, every single archetype in the "manager" section of this site contains advice which runs exactly counter to the advice from the also highly-upvoted "Common Mistakes of New Engineering Managers" article currently on the HN home page. This just goes to show the extent to which our industry is still very "unsolved" and contains a multitude of often completely-opposed opinions - which means that r…
Re: How to deal with difficult people on software projects
#63Earlier quoted context omitted.
I literally don't know how else to deal with certain categories of folks with whom talking and trying to resolve the issue has no effect. Going around them/ignoring them is literally the advice you get from basically every literature I've read, and I've read a lot about this. But you do have to try to work through the issue first, and you have to be willing to try again if they seem open to resolving the problem down…
What would you suggest from your readings? I've mostly benefited from hard realism approach and Actor theory (as applied by some: everyone has an agenda, to work with them: Align, make Peace, or Destroy).
The reasoning in the literature for avoiding this topic is sound. If you provide the "destroy" option to folks, they're usually going to go with that pretty quickly, and only nominally go for the other methods of resolving conflict.
I've had someone make that determination about me at a previous role, which then put me obviously in a "what do I do with this person?" position which itself led me to the "ignore/destroy" answer. If it hadn't been an option, would this person and I have had a more pleasant working environment?
Re: How to deal with difficult people on software projects
#64Earlier quoted context omitted.
Fully agreed. Amusingly, every single archetype in the "manager" section of this site contains advice which runs exactly counter to the advice from the also highly-upvoted "Common Mistakes of New Engineering Managers" article currently on the HN home page. This just goes to show the extent to which our industry is still very "unsolved" and contains a multitude of often completely-opposed opinions - which means that r…
Management has been around since ancient times in various forms. There are things that kinda work, but the game keeps changing as the interests and balances of power shift in the workplace. Why would it ever be "solved"?
Re: How to deal with difficult people on software projects
#65> There is no “solution” to The Rockstar Developer
> It is impossible to solve The Aspiring Manager
> The Extreme Overestimator... is fixable, but there is no will to fix it.
> if The Incompetent Developer had the capacity to learn software development, they would have already
> All in all, [The Soldier is] nearly an impossible problem to fix.
> There is no fixing The Legacy Maintainer
At least having disabused ourselves of the ability to actually try to address issues, we can now get rid of management since they clearly have no work to do!
Re: How to deal with difficult people on software projects
#66Re: How to deal with difficult people on software projects
#67If this is posited as actual guidance for interpersonal communication, run.
Re: How to deal with difficult people on software projects
#68This is a horrible website and you will likely experience diminished tenure if you follow it's advice. First, there is a complete lack of empathy for the person being labelled. What are the motivations and constraints that led to this person acting this way? A key question and the foundation for building healthy productive relationships. Second, the 'solutions' are horrible. "Go around the person" is terrible advice…
Re: How to deal with difficult people on software projects
#69This is a horrible website and you will likely experience diminished tenure if you follow it's advice. First, there is a complete lack of empathy for the person being labelled. What are the motivations and constraints that led to this person acting this way? A key question and the foundation for building healthy productive relationships. Second, the 'solutions' are horrible. "Go around the person" is terrible advice…
The only one that kind of bothered me was "The Legacy Maintainer" which argues that your legacy maintainers _want_ to be stuck on a legacy project with their career in ruins. In my experience, nobody wants that, but neither can they do anything about it. Then again, the world already looks down on LM's as effectively an "untouchable" caste, so any excuse will do.
It's something you have experience with, and therefore feel empathy for. Is it likely that you just happened to have experience with the one "role" that's worth being empathetic towards?
Re: How to deal with difficult people on software projects
#70I'm sensing a pattern in these answers: > There is no “solution” to The Rockstar Developer > It is impossible to solve The Aspiring Manager > The Extreme Overestimator... is fixable, but there is no will to fix it. > if The Incompetent Developer had the capacity to learn software development, they would have already > All in all, [The Soldier is] nearly an impossible problem to fix. > There is no fixing The Legacy Ma…
I say this as a soldier myself.