3 ms·

Could you provide some examples of times when being arrogant improved the quality of the product you delivered? I've certainly run into arrogant engineers in t

Could you provide some examples of times when being arrogant improved the quality of the product you delivered? I've certainly run into arrogant engineers in the past. I spent the 2-3 weeks after the worst of them left cleaning up his bug-ridden, brittle code. If he had worked more collaboratively, it wouldn't have had to be that way.

myWindoonn 8y ago
Correctly identified that a product would be a GDPR problem. Said product's main feature was deanonymizing non-consenting visitors. Insisted that certain metrics should be recorded, ended up identifying massive gaps in SLA, improved overall QoS. Was asked to give SRE and Devops advice to a team. Told them to document their "regular tasks"; that is, to write down a doc "How to Upgrade Frob Databases" so that they would have a way to do all the "Upgrade Frob Database for Customer #xxx" tickets on their kanban board. Got pushback. Wrote the docs for them anyway. Their kanban board drained over the next two sprints. Edit: In all cases, got massive pushback from management and never from devs nor engineers. Was called "arrogant", "troublemaker", "enabler", reprimanded, etc. You asked for examples, you get examples.
- ThorinJacobs 8y ago
  Forgive me, but these don't sound like instances of arrogance. You've pointed out flaws in execution or feature, and I would do the same, but that's not arrogance. That's just doing your job as a developer. Maybe you achieved these in an arrogant way? I'm not going to deny that you can get things done being arrogant. But I don't think it's necessary to getting things done right.
  - pdimitar 8y ago
    I think he is saying that he got labeled as arrogant because he was not respecting internal office drama and human specifics which were getting in the way of him trying to do his job well. Is that arrogant? It's very context-specific but I'd claim that most of the times it is not. People calling other people offensive names in offices happens way too many times. Way too many managers and teams got too warm & fuzzy & comfy (and unproductive) and any newcomers who want to get shit done are labelled as "rocking the boat" although not literally but with a ton of euphemisms to conceal the core idea -- like those your parent commenter already mentioned ("troublemaker" etc.).
wolfgke 8y ago
> Could you provide some examples of times when being arrogant improved the quality of the product you delivered? Being arrogant and being perceived by other people as arrogant are two completely unrelated pairs of shoes. I personally would assume that many "nerds", for a lack of "social fluency" (I want to avoid the term "social skills", since in my experience they are not socially "unskilled", but rather think differently from many other people, which makes them often act somewhat clumsily), are perceived as arrogant, while they actually are not. On the other hand, I observe that many people who play the "acting humbly" game are actually deep inside quite arrogant and narcistic.

myWindoonn 8y ago

Correctly identified that a product would be a GDPR problem. Said product's main feature was deanonymizing non-consenting visitors. Insisted that certain metrics should be recorded, ended up identifying massive gaps in SLA, improved overall QoS. Was asked to give SRE and Devops advice to a team. Told them to document their "regular tasks"; that is, to write down a doc "How to Upgrade Frob Databases" so that they would have a way to do all the "Upgrade Frob Database for Customer #xxx" tickets on their kanban board. Got pushback. Wrote the docs for them anyway. Their kanban board drained over the next two sprints. Edit: In all cases, got massive pushback from management and never from devs nor engineers. Was called "arrogant", "troublemaker", "enabler", reprimanded, etc. You asked for examples, you get examples.

ThorinJacobs 8y ago
Forgive me, but these don't sound like instances of arrogance. You've pointed out flaws in execution or feature, and I would do the same, but that's not arrogance. That's just doing your job as a developer. Maybe you achieved these in an arrogant way? I'm not going to deny that you can get things done being arrogant. But I don't think it's necessary to getting things done right.
- pdimitar 8y ago
  I think he is saying that he got labeled as arrogant because he was not respecting internal office drama and human specifics which were getting in the way of him trying to do his job well. Is that arrogant? It's very context-specific but I'd claim that most of the times it is not. People calling other people offensive names in offices happens way too many times. Way too many managers and teams got too warm & fuzzy & comfy (and unproductive) and any newcomers who want to get shit done are labelled as "rocking the boat" although not literally but with a ton of euphemisms to conceal the core idea -- like those your parent commenter already mentioned ("troublemaker" etc.).

wolfgke 8y ago

> Could you provide some examples of times when being arrogant improved the quality of the product you delivered? Being arrogant and being perceived by other people as arrogant are two completely unrelated pairs of shoes. I personally would assume that many "nerds", for a lack of "social fluency" (I want to avoid the term "social skills", since in my experience they are not socially "unskilled", but rather think differently from many other people, which makes them often act somewhat clumsily), are perceived as arrogant, while they actually are not. On the other hand, I observe that many people who play the "acting humbly" game are actually deep inside quite arrogant and narcistic.