As a Manager: What I value in developers
codemonkeyism.com
codemonkeyism.com
My question to the author is: how do /you/ balance the need for craftsmanship against deadlines? Most managers pay lip service to quality at best, some don't even do that. How do you meaningfully encourage your professionals to craft carefully?
Of course, English may not be his first language, so I am certainly not trying to condemn him, but it is still ironic in an essay that spends substantial time talking about not cutting corners.
If it is a large project where the new developer will have to work on a team, than being able to work with and coordinate with that team are almost more important than just being able churn out the code. After all, if he writes beautiful code that no one else can interface with than it is of little value.
Also, in technology a willingness and ability to learn are vital in a long term employee. The technology will continue to change, if the new employee is not willing and able to change with it than they will not remain valuable for the long haul, and with the difficulty of firing people in large organizations that can be a major problem.
Craftsmanship and an ability to "get things done" should certainly be criteria and high on the list, but they should not be the only ones in most cases.
See here: http://bobsutton.typepad.com/my_weblog/2009/10/selecting-tal...
Short term view: Superficial markers of success are most highly valued.
But in the long run: Intellectual power matters most.
(sigh)