My humble experience is different. There is no surer way to create shitty, incoherent code, flaky tests, architecture mistakes, and Rube Goldberg machines, than when trying to satisfy various people in your org.
Junior stays a junior in my book until they learn to "satisfy code" or to bring elegance instead of primarily satisfying specific people.
If Henry Ford was listening to customers, he would start breeding a faster horse. That perfectly shows that ego can have a good side.
Re ego, I think maybe the vocabulary choice is misaligned here. Anyway, these days, "team player" is becoming a sarcastic innuendo.
Junior stays a junior in my book until they learn to "satisfy code" or to bring elegance instead of primarily satisfying specific people.
If Henry Ford was listening to customers, he would start breeding a faster horse. That perfectly shows that ego can have a good side.
Re ego, I think maybe the vocabulary choice is misaligned here. Anyway, these days, "team player" is becoming a sarcastic innuendo.