Q.
A. There's no real clearcut answer because it will vary by location/demand, etc. I did a search on salary.com and they define systems administrator's job duties as the following:
Installs new software releases, system upgrades, evaluates and installs patches and resolves software related problems. Performs system backups and recovery. Maintains data files and monitors system configuration to ensure data integrity. May require a bachelor's degree in a related area with at least 2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a project leader or manager.
Their chart suggests that the US average base salary for such a job is between $60k and $77k.
As a comparison, the job of "Help Desk Support" with the following duties:
Provides support to end users on a variety of issues. Identifies, researches, and resolves technical problems. Responds to telephone calls, email and personnel requests for technical support. Documents, tracks and monitors the problem to ensure a timely resolution. May require an associate's degree in a related area and 0-2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a supervisor or manager.
... makes on average between $38k and $48k.
Not sure what your idea of a "novice" sysadmin is, but I would guess that it falls somewhere between the two.
Installs new software releases, system upgrades, evaluates and installs patches and resolves software related problems. Performs system backups and recovery. Maintains data files and monitors system configuration to ensure data integrity. May require a bachelor's degree in a related area with at least 2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a project leader or manager.
Their chart suggests that the US average base salary for such a job is between $60k and $77k.
As a comparison, the job of "Help Desk Support" with the following duties:
Provides support to end users on a variety of issues. Identifies, researches, and resolves technical problems. Responds to telephone calls, email and personnel requests for technical support. Documents, tracks and monitors the problem to ensure a timely resolution. May require an associate's degree in a related area and 0-2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a supervisor or manager.
... makes on average between $38k and $48k.
Not sure what your idea of a "novice" sysadmin is, but I would guess that it falls somewhere between the two.
How much of the Microsoft Office Suite do you really use?
Q. In my role as an Administrative Assistant I am always on the computer. I suspect the most important skill I have to offer the company is my knowledge in the various Microsoft Office Suite Software Packages (Word, Excel, Powerpoint, Access, Outlook)
I do things every week that connect with each and every one of these software packages (Correspondence, Spreadsheets, Presentations, Charts, Graphes, Databases, Email, Setting up Meetings, Organizing Tasks, etc)
How much of the various Microsoft Office Packages do you really know in comparison to the various features of each software packages?
I do things every week that connect with each and every one of these software packages (Correspondence, Spreadsheets, Presentations, Charts, Graphes, Databases, Email, Setting up Meetings, Organizing Tasks, etc)
How much of the various Microsoft Office Packages do you really know in comparison to the various features of each software packages?
A. The only portion I don't use on a daily basis is Powerpoint. How in depth each one gets used depends on what I need to get done. Outlook is my most heavily used package. I use it for everything, including "sticky notes" since I can't stand having little sticky pieces of paper all over my monitor that later fall off onto my desk.
Word is used to create templates for forms, correspondence, creating/maintaining the intranet website, etc. Excel gets used to create charts, check off lists, and any other use where Word isn't practical. Access is used to track the ongoing details for every project. The database is syncronized each day with the sister database at the corporate office. All the data contained in the database is accessed via software that was programmed in-house. I am responsible for maintaining the databases and programming all upgrades to the software. I also have used Access to create a graphical interface for a database that is used by the warehouse.
Word is used to create templates for forms, correspondence, creating/maintaining the intranet website, etc. Excel gets used to create charts, check off lists, and any other use where Word isn't practical. Access is used to track the ongoing details for every project. The database is syncronized each day with the sister database at the corporate office. All the data contained in the database is accessed via software that was programmed in-house. I am responsible for maintaining the databases and programming all upgrades to the software. I also have used Access to create a graphical interface for a database that is used by the warehouse.
If you possess a mainframe computer to develop a suite of programs, don't you need another mainframe computer
Q. to check that the programs running on the first mainframe can be built from the audit trail of changes.
don't you need a third mainframe to check that all is well.
To ragdefer
Thanks. Terrific insight.
To Brett T.
Thanks. Terrific insight.
my thinking in asking the question was:
There needs to be a chain of custody of a program.
You won't be able to detect if the software has been doctored, without some sort of audit trail information.
Checksum information would suffice.
To Al,
Thanks. Terrific insight.
don't you need a third mainframe to check that all is well.
To ragdefer
Thanks. Terrific insight.
To Brett T.
Thanks. Terrific insight.
my thinking in asking the question was:
There needs to be a chain of custody of a program.
You won't be able to detect if the software has been doctored, without some sort of audit trail information.
Checksum information would suffice.
To Al,
Thanks. Terrific insight.
A. Audit trail of changes is a separate animal than rebuilding programs.
Are you at all familiar with mainframes?
There was some phony baloney news articles a few years back claiming that mainframes were passe, so a bunch of people left the industry to get out early, career change. This meant that right now, and for several years, there has been a severe shortage of staffing for mainframe shops.
The reality is that there are applications that make sense to be run on super computers, mainframes, server farms, mini-computers, desk top units, engineering platforms, etc. etc. but of course many are run on inappropriate platforms.
Both mainframes, and midrange computer sizes (a server farm in a single box) have partitions and librarries and environments, where software files production testing can be kept separate.
There are people who can access certain sub-groups of production files, production software, testing environments and so forth.
Now there are companies that have one computer network for production, and another for testing. one advantage of this setup is if you have a severe hardware hassle, you can backup the test hardware, and have it switch places with the one that is in trouble. This sort of thing is getting rarerr and rarer these days thanks to RAID on mission critical networks, where ANYTHING is interchangeable without having to bring the system down.
When you hear in the news media of some crash at an airport, electrical gneeration place, nuclear power plant, or other place that ordinary people might think is mission critical, it is usually because the people in charge tried to save money by getting rid of redundancy.
I work on an IBM midrange computer that has a version of the IBM Universal Data Base System. A really cool tool is their file to file comparison. You can compare any two versions of the same kind of object.
program to program
file to file
report to report
you name it
You get a line by line chart of what is different between the two copies.
Where this can be a HUGE help.
We have program XYZ that we bought from some company
We have made a bunch of modifications to program XYZ
Different people are working on different modifications in testing
Along comes a new release of the software from the original company & their documentation of what they changed is for the birds.
So we run the data base comparison tool
original software vs. latest from the vendor ... get a list of the 1,500 or so lines of code that they inserted, changed, or deleted
also original software vs. the version we now have in production
1,000 or so lines of code that we inserted, changed, or deleted
Now we have the tools to figure out where all involved to try to merge the two paths of changes
Are you at all familiar with mainframes?
There was some phony baloney news articles a few years back claiming that mainframes were passe, so a bunch of people left the industry to get out early, career change. This meant that right now, and for several years, there has been a severe shortage of staffing for mainframe shops.
The reality is that there are applications that make sense to be run on super computers, mainframes, server farms, mini-computers, desk top units, engineering platforms, etc. etc. but of course many are run on inappropriate platforms.
Both mainframes, and midrange computer sizes (a server farm in a single box) have partitions and librarries and environments, where software files production testing can be kept separate.
There are people who can access certain sub-groups of production files, production software, testing environments and so forth.
Now there are companies that have one computer network for production, and another for testing. one advantage of this setup is if you have a severe hardware hassle, you can backup the test hardware, and have it switch places with the one that is in trouble. This sort of thing is getting rarerr and rarer these days thanks to RAID on mission critical networks, where ANYTHING is interchangeable without having to bring the system down.
When you hear in the news media of some crash at an airport, electrical gneeration place, nuclear power plant, or other place that ordinary people might think is mission critical, it is usually because the people in charge tried to save money by getting rid of redundancy.
I work on an IBM midrange computer that has a version of the IBM Universal Data Base System. A really cool tool is their file to file comparison. You can compare any two versions of the same kind of object.
program to program
file to file
report to report
you name it
You get a line by line chart of what is different between the two copies.
Where this can be a HUGE help.
We have program XYZ that we bought from some company
We have made a bunch of modifications to program XYZ
Different people are working on different modifications in testing
Along comes a new release of the software from the original company & their documentation of what they changed is for the birds.
So we run the data base comparison tool
original software vs. latest from the vendor ... get a list of the 1,500 or so lines of code that they inserted, changed, or deleted
also original software vs. the version we now have in production
1,000 or so lines of code that we inserted, changed, or deleted
Now we have the tools to figure out where all involved to try to merge the two paths of changes
Powered by Yahoo! Answers
No comments:
Post a Comment