Hackers and Suits: 10 Tips for Managers to Bridge the Gap
Managers and software developers live in two separate worlds. An expert programmer shares his advice about how to motivate, communicate with and (maybe) understand these strange people who build the software solutions upon which you rely.
Thu, October 18, 2007
CIO — There is a Great Divide in the realm of information technology. I'm not talking about Windows versus Linux or Java versus .NET—no, nothing like that. The gap I'm referring to is between software developers and the people who manage them—what I call hackers and suits.
Let's clarify one thing first: The word hacker is used in at least three senses. There is the Hollywood sense of a kind of "digital burglar" (more properly called a cracker); there is the sense of a person who throws software together quickly and without skill or caution; and finally there is the "true" sense of the word: a craftsman who is a master at what he does, knowledgeable and capable.
It's the third sense I'm concerned with here. If you're unfamiliar with this usage, refer to the Jargon File or even better, read Paul Graham's excellent essay "Hackers and Painters."
And what is a "suit"? Well, if you don't know what one is, you might be one. The term is common (though not universal) slang for a manager—deriving, of course, from the contrast in dress code. In many or most firms, developers are permitted to dress casually. Managers tend to wear suits—in some cases even appearing to like wearing them—and this sometimes puts developers on their guard.
This article has been difficult to write; it is not dispassionate or unbiased. I am a senior developer with no management background, which places me firmly in one camp. But honesty compels me to admit that neither side is wholly right or wholly wrong in its attitudes. There are certainly things that hackers can learn from suits, and vice versa. The gap can be bridged—has to be bridged—if a department is to run smoothly.
The other reason for my difficulty is that I am writing for the other group—the one to which I don't belong. But bear with me, and I will try to be fair.
First of all, it helps to understand where the hacker is coming from. Software is a strange thing—it is abstract and malleable since it is written in some kind of language—but it is also like a machine in that it has to be precisely correct and has to function properly. Software development is a hard skill to acquire, and mastering it often gives the practitioner a kind of tunnel vision. The hacker may worry about many aspects of his code, such as readability, portability, maintainability and performance; but his code is basically his world.
