Quote:
Originally Posted by Sarlacc
-Imagine a young, bright and opinionated programmer. Wearing dreadlocks and a smelly t-shirt that says "1337 h4x0r".
His boss says "I'm gonna have to pull you off that leading-edge project with the 3D app, we need you to go fix bugs in someone else's crap code on that system I know you think is solid junk. For about a year or so. Okay?"
That leader will need all the tricks in the book, and some genuine people skills, to get good performance out of the programmer.
|
Quote:
Originally Posted by Dadhawk
All you are going to accomplish in this scenario is losing your best programmer and now still having crap in one system, and the other getting behind.
The better option is to assign the "star" to spend part of his week working with the other team to help up their skills with some selective bug fixes while allowing her to continue to work on the primo project she really has an interest in.
|
Aha! This is interesting.
I was about to mention the assumption made that the hypothetical company had enough resources. Then I realized that even if the other "team" consisted of one person, your solution would likely still apply.