When I act as a hiring manager, I take a slightly different tract from this essay. Professionalism (by which he seems to actually mean craftsmanship) and "getting things done" are certainly important, but they are neither enough nor necessarily the most important things.
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.
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.