Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re^2: Making the Business Case for Developer-Run Development

by etcshadow (Priest)
on Aug 11, 2004 at 02:09 UTC ( #381837=note: print w/replies, xml ) Need Help??


in reply to Re: Making the Business Case for Developer-Run Development
in thread Making the Business Case for Developer-Run Development

I'm not really sure how Graham's article applies.
Well, he does talk about it in a few different places, but I don't think it could be more clear how he feels on the matter when he says:
I've seen occasional articles about how to manage programmers. Really there should be two articles: one about what to do if you are yourself a programmer, and one about what to do if you're not. And the second could probably be condensed into two words: give up.
He then goes on to justify this statement with a few paragraphs, too.
------------ :Wq Not an editor command: Wq

Replies are listed 'Best First'.
Re^3: Making the Business Case for Developer-Run Development
by adrianh (Chancellor) on Aug 11, 2004 at 09:30 UTC
    He then goes on to justify this statement with a few paragraphs, too.

    Unfortunately I don't find the justification that compelling :-) The only management problem specific to non-developers he talks about is "if you're not a hacker, you can't tell who the good hackers are".

    First, there is an element of recursion there (how to you hire the great hacker that knows who good hackers are since you can't tell who a good hacker is?)

    Second there is nothing special about software development. The same is also true of all skilled professions (how do you know who the good designer is if you have no aesthetic skills, etc.)

    If hiring people is the only problem there are many simple solutions that good managers already know about (e.g. specialised head hunters, consulting in-house experts, auditions, etc.)

    Graham's article is a good read - but to my eyes it's about hiring great hackers to code, not hiring great hackers to manage. He even discusses mechanisms for isolating them from end-users to get them productive. Hardly a feature for a manager!

    The other time he talks about management:

    This is an area where managers can make a difference. Like a parent saying to a child, I bet you can't clean up your whole room in ten minutes, a good manager can sometimes redefine a problem as a more interesting one. Steve Jobs seems to be particularly good at this, in part simply by having high standards.

    he's talking about Steve Jobs - a non-developer.

    So I come back to the question - what exactly is your manager role's responsibilities, and why do you think that a non-developer won't be able to do them?

    (I'm not trying to say that a developer would necessarily be bad for the role. Good managers with a techie background do exist. I'm just saying that, for a management role, I'd be more interested in good management skills rather than good software development skills. Better a good manager with no developer experience than an average manager with developer experience. Good managers can learn what the need to know.)

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://381837]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (3)
As of 2022-01-16 18:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:












    Results (49 votes). Check out past polls.

    Notices?