I don't see a single reference to backstabber, empire builder, or middle management machiavelli. Maybe ladder climber, but who in "management" isn't in the ladder climbing business?
How to deal with difficult people on software projects
111–120 of 130 posts
Re: How to deal with difficult people on software projects
#112All these archetypes can be consolidated to one: "narcissist".
Capitalism is fundamentally about self-interest.
Narcissism is fundamentally about self-interest.
In corporate workplaces, teamwork is simply a temporary treaty imposed by higher level capitalists/narcissists so that you do their bidding, not yours.
If you are working in a corporation, you are almost certainly doing things for narcissistic reasons (for some definition of narcissism/self-interest/self-gratification/self-actualization).
Many of the "antipatterns" are really defense mechanisms from the fundamental hobbesian nature of a workplace.
Re: How to deal with difficult people on software projects
#113Earlier quoted context omitted.
the first thing I ask myself in this sort of situation is whether the person is actually correct. part of being effective in a specific role is refusing to take on random work people throw at you. estimates can't be valid if key players are spending lots of time on stuff that wasn't on the schedule. if the person is really just being obstructive, explain to their manager (or have your manager explain to that manager)…
Worked in an environment were anything vague in ticket/story would cause team to reject considering it. At first I was horrified at this. “You can’t tell the boss no!” Six months later I had to admit it was by far the most productive team I had or have ever been on.
huh, they should be writing up their own after building a shared understanding of the problem in hand, what you experienced was a top down ticket factory
Re: How to deal with difficult people on software projects
#114What a toxic little website. Do not follow the advise here. Do not label your co-workers. Trust them, listen to them. If you see them exhibit traits you perceive as negative (and fall into these crude buckets) - talk to them, and give them feedback. Chances are, they will appreciate it, and your working relationship will improve.
That was my thinking when I started reading it. The site is missing an archetype: The Zebra, a developer who sees everyone around them in black and white terms and focuses on calling out problems for all to see rather than fixing them as quickly and gently as possible.
Ah, anyway, I was hoping to find a little disclaimer somewhere saying not to take this exercise too seriously.
Re: How to deal with difficult people on software projects
#115The author is clearly a developer, as there are some positive stereotypes in that category, but no positive stereotypes in any other category. I'm guessing their perspective on the related roles is either only through the lens of a developer, or through no lens at all, just squinting from afar.
The site is titled "how to deal with difficult people..." Not nice, competent, or all people, just a specific negative subtype. I totally agree with the comments about not stereotyping coworkers. The way this site is setup is naturally contrarian to that idea.
While that is the title of the site, the site also has an entire section dedicated to "Dev Types" which all sound like a one-sided glorification of highly questionable developer behaviors.
Everything about this site feels gross.
Re: How to deal with difficult people on software projects
#116I'm fine being labeled an idealist. Depending on the client or employer, this role has served me well. On occasion, there is no space for an idealist and if alignment can't be carved out, I'm happy to move on. Now. Where can a 57yo idealist find a job in today's world?
Ha! In your dreams.
Re: How to deal with difficult people on software projects
#117Reading some of the comments here (and the vitriol), am I wrong in thinking that this site was meant as a joke? Because I totally read it as such...
Re: How to deal with difficult people on software projects
#118Whilst technically leading a software project, I worked with a contractor who was so arrogant it defied belief. He told me he was smarter than everyone else in the organisation, and repeatedly told me that he used to work "at board level" whenever he wanted to override my decisions. You know what - I'm fine for anyone in a team to express different opinions and happy to take them on board, but there's a way of going…
If you were his manager, why couldn’t you can him?
Re: How to deal with difficult people on software projects
#119Reading some of the comments here (and the vitriol), am I wrong in thinking that this site was meant as a joke? Because I totally read it as such...
I read it as a bit of fun ... I feel everyone's maybe taking this a bit too seriously.
Re: How to deal with difficult people on software projects
#120Software engineers have the privilege of being at or near the top of the food chain when it comes to job mobility. I follow a very simple rule - if I hate something about my job and it can't be fixed in the mid term, I look a new job. Overthinking this easily leads to burnout and frustration.
"If you can't change your job, change your job"