[leroman]

Being a consultant for a considerable part of my career, whilst sometimes working solo on writing a system from scratch.

In one example, re-writing a system written by 7 team members + architect, taking half the time.. Maybe due to working in an organization without a formal org position.. I had to make sure bad requirements, process, tech decisions etc.. don't get in the way of properly collecting requirements, designing and building this system, seen today as a hugely successful project for this company. I have to say, some people see me as an asshole, no doubt, other's see me as a bulldozer that got the work done and stand behind me and keep in touch to this day.

Our interaction will depend heavily on if you are in my way or not, though I don't consider my self toxic or hoarder of information.

[marcus_holmes]

I'm glad this appears to give you some satisfaction, but I hope I never have to work with you, or around you, or on any project you've worked on.

[patrec]

This cuts both ways, smart and competent people might also not like to work with you or any project you've worked on.

I have no real insight into your personality and ability (but neither do you about GF).

Competent people who want or need to fix some dysfunctional monstrosity committed by a coherent group of less able developers are not necessarily welcome, even if they don't have pathological personality traits. All the more if they are not parachuted in to fix something, but e.g. some new starter not high up in the hierarchy. Consider that few people take kindly to being told (if only by implication) that what they've done is garbage, but obviously the world is full of garbage software.

I've seen this time and time again. Long-term diplomacy can sometimes work (assuming the company and individual have the time to spare), but they'll usually need some higher up backing or fail miserably/leave/get-fired.

[tonyedgecombe]

I've been brought into several moribund projects similar to what @leroman is describing. Usually you are there to push past the bullshit. Often the problems start with someone similar to what you described in your original post.

[username90]

What is wrong with ignoring and working around toxic people who only undermines the project?

[leroman]

Ignoring sounds passive but there is nothing passive about telling people their ideas and cooperation is unproductive (be it people from product, RnD, management, QA etc), you spend much time and energy convincing them their ideas are not concrete, or are going in a bad direction, or are simply bad.. Having the burden of completing the project (successfully!) on me, I have to cut through the BS and provide results, not attend to egos and fragility of everyone involved.. Never the less, I try to be dry and not personal as I can to communicate the situation as simple as possible to the other party.. In my consulting career I learned that being "nice" is not worth it and ends up costing me in mental health..

[perl4ever]

"re-writing a system written by 7 team members + architect, taking half the time"

Sure, but are you saying this is about individual productivity or had you considered it might be the costs of coordination?

[leroman]

I wasn't meaning to say anything about the "why", just the facts.. For starters, the project I was working on was a success, the other failed.. so its not even comparing the same thing.

Just offering my anecdotal story as a potential "asshole" offender per OP