27 ms·

"It was an excellent argument against "inflated opinion of self importance" though. If you write something that's as widely used by developers as homebrew, you'

"It was an excellent argument against "inflated opinion of self importance" though. If you write something that's as widely used by developers as homebrew, you've earned that right." No, you actually never earn that right. Seriously. In fact, it's a sign of good engineers that they just view their stuff as stuff, and not "well, i am doing the super important stuff, everyone else is not". Note that this is different than prioritizing, etc. If you have a bunch of high level engineers in a room, and they don't value each other's work (IE recognize that a lot of stuff is "important", and there stuff is just part of that) because they think the stuff they do is super-important, that's going to go very badly. At lower levels, pretty much none of it is so important that there is any value to having an inflated opinion of self importance. The fact that you've achieved adoption does not necessarily make you a good engineer.

gcp 10y ago
"well, i am doing the super important stuff, everyone else is not". Straw man argument. Nobody stated this. There's also a difference between thinking that your stuff is super important in isolation versus simply pointing out it's in wide use at a company and hence your previous efforts have in fact been productive and useful for them.
- DannyBee 10y ago
  "Straw man argument. Nobody stated this." This is pretty much exactly his attitude, even if he did not explicitly add the other 3 words. "in wide use at a company and hence your previous efforts have in fact been productive and useful for them." Except that assumes it's literally true. It's not, as a downvoted person said :) It also assumes that him working on it would be useful or productive relative to doing something else. That is also probably a negative.