To summarize, the article suggests making the "software science" job title to:
* "reduce career path anxiety"
* "enhance engineering organizations' self-understanding"
* "advance the general understanding of the right way to develop software"
* "raise awareness about the sponsoring engineering organization"
* "bring out some of those 'big picture' thinkers from the woodwork"
The third point is the only one close to the traditional role of a scientist, though "general understanding" takes more than data and statistics from a single organization. Otherwise, this seems to be a pretty blatant misappropriation of the name "scientist"!
Comments
To summarize, the article suggests making the "software science" job title to:
* "reduce career path anxiety" * "enhance engineering organizations' self-understanding" * "advance the general understanding of the right way to develop software" * "raise awareness about the sponsoring engineering organization" * "bring out some of those 'big picture' thinkers from the woodwork"
The third point is the only one close to the traditional role of a scientist, though "general understanding" takes more than data and statistics from a single organization. Otherwise, this seems to be a pretty blatant misappropriation of the name "scientist"!