3 ms·
No, they do not. There isn't even a consensus on what "great" means. You play basketball in a very static environment. The rules don't change from game to game
by BeetleB 6y ago
No, they do not. There isn't even a consensus on what "great" means.
You play basketball in a very static environment. The rules don't change from game to game, or team to team. The duration of a match is constant. How well the team performs is a well known metric.
People do not do engineering in a static environment. The needs asked of one changes from team to team. The quality metrics vary from application to application. The people he/she relies on varies even when you stay in the same team. An engineer who is really useful in one company may be harmful to another one.
- llimllib 6y agoI suspect you haven’t played much basketball! The same player on different teams can be much better or worse - some players fit in with almost any team and others need a team built around them. (I don’t disagree with your larger point! Just that basketball is an example of a “very static environment“ relative to programming)
- cortesoft 6y ago> You play basketball in a very static environment I would strongly disagree - basketball is a highly dynamic environment, simply because you have an opponent. Everything you are trying to do, you have someone else trying to stop you. They are as adaptive as you are. Because of this dynamism, many players who were great in previous eras couldn't survive in the modern era (and vice versa, really)... for example, most centers who played even 10 years ago would be abused in the modern game by opposing centers shooting threes. It simply wasn't part of the game 10 years ago, and now everyone does it. There was literally a player (Roy Hibbert) during the transition who was a star before and suddenly became unplayable as teams adapted to the new environment. He was out of the league in 2 years.
- username90 6y agoSoftware engineer is too many things. The person implementing a database engine working in a huge tech organization and the person implementing non scaling crud services as the only technical person in the company are both software engineers but what they need to be great are almost completely disjoint.