Jonathan Hutchins wrote:
> Hal Duston wrote:
>
> > Source Code Configuration Management
> > *  CVS
> > *  Subversion
> > *  Visual Sourcesafe a plus
>
> I would think that would be the responsibility of the software
> project manager.  Putting under the SysAdmin pretty much
> guarantees you get a programming orientation to the job,
> rather than a systems and support orientation.

There is plenty a sysadmin can do with sourcesafe without needing to know about branching, labelling, and pinning... They can perform nightly maintainance, scan logs, and be familiar with the various forms of data corruption that occur and how to recover from them. They can split and merge repositories. Try vainly to make it more secure through the use of shadow folders, etc.

> A lot of people don't appreciate the fact that a good programmer
> is NOT the same thing as a good system administrator.

True. Consistent, cautious, conservative, and reliable are not the hallmarks of most programmers. Nor a willingness to perform tasks of a repetitive nature.

Just as there is a world of difference between a database administrator and a database architect, a good systems administrator is not the same thing as as a good systems architect.

Administering a system is different than designing one. If you have a well architected system, you won't need as many sysadmins.

The best sysadmins I've encountered have almost always come from a software or database developer background. They usually end up as the systems architects... but their job title more likely still reads "senior sysadmin".

--
Garrett Goebel
IS Development Specialist

ScriptPro                   Direct: 913.403.5261
5828 Reeds Road               Main: 913.384.1008
Mission, KS 66202              Fax: 913.384.2180
www.scriptpro.com          garrett@scriptpro.com