I agree about job descriptions not being what the job entails and that is where organizations like LOPSA have to be on the forefront to have these descriptions to keep the profession (not job) from becoming diluted. In my prior life as a Maintenance Machinist with the US Mint I watched how the Government took a trade (Machinist) and with the stroke of the pen make the job a Mechanic's job. Now I am not downing a mechanic but the title of Machinist was for an Apprenticable trade while the mechanic was not. Also with that the upward progression went away and the pay was downgraded accordingly.
So there is a lot that goes with the name. Granted some things can't be stopped but System Administration is a Profession and the Description should back that up. John J. Boris, Sr. JEN-A-SyS Administrator Archdiocese of Philadelphia "Remember! That light at the end of the tunnel Just might be the headlight of an oncoming train!" >>> "Brodie, Kent" <bro...@mcw.edu> 5/4/2010 4:27 PM >>> I would say this is where we want to go - and what we as LOPSA members should (partly) be about-- spreading the word what a "sysadmin" is, and does. I second the opinion that a good sysadmin is well-rounded, is WELL versed in networking too, etc. But, as time marches forward, the perception of the sysadmin role by companies-- especially HR departments, is where things tend to unravel. I have seen job descriptions for systems administrators that were nowhere near what I thought those jobs should be, and I've also seen job titles of "Network Engineer" where the job description was essentially-- a sysadmin! The disconnect is fairly large, depending on the company. "Read the fine print", I guess... _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
