Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Good sysad/programmers are rare

by blssu (Pilgrim)
on Sep 20, 2002 at 19:58 UTC ( #199609=note: print w/replies, xml ) Need Help??

in reply to Re: Beginning Perl for system admins
in thread Beginning Perl for system admins

... because both jobs are damn hard!

I think the "programmers can't be sysads" folklore comes from two beliefs: (1) sysads and programmers were adversaries back in the days when programmers fed stacks of cards to the Machine God behind the glass window, and (2) programmers are theorists with no concern for the real world, while sysads Get Jobs Done.

In truth, the same basic skills apply to both jobs. Sysads need to handle pressure a bit better. Programmers need to handle abstraction a bit better. Sysads tend to use lousy tools too, so secondary skills like record keeping are more important for sysads.

The biggest problem both jobs have is the folklore that people can learn them by taking some ad hoc training. Many people without formal training have become good sysads and programmers. The big lie is that people don't need structured, progressive, disciplined training. They do. If someone doesn't have the self discipline to do that independently, he or she really needs the support of a university. (or monastery ;)

Replies are listed 'Best First'.
Re: Good sysad/programmers are rare
by rinceWind (Monsignor) on Sep 20, 2002 at 23:30 UTC
    Thank you blssu for enlightening me as to where the dichotomy between sysadmins and programmers comes from. Also thank you for boosting my confidence convincing me that people with my skills are in short supply.

    Although I have a computer science degree, and other training as a programmer, I have always had a "let's peep under the hood" approach to what I am doing. I believe there is a huge overlap, including "Technical Support Consultant" and "Systems Programmer" - both roles I have done (technical support is what I am doing at present).

    I see the solution, not in terms of external discipline (University or PM), but in terms of changing the attitude of colleagues in work environments. I believe it is really a question of leadership.

    Being a self confessed jack of all trades, I see no reason why people with a particular job description should always stick together, forcing work into vertical silos. The much better structure is smaller - cross discipline - teams, where everyone is working towards the same goals. These are: solving the client's problems, delivering software solutions and making money for your employer's business.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (3)
As of 2023-10-04 22:38 GMT
Find Nodes?
    Voting Booth?

    No recent polls found