I guess it matters what sort of system
administratory you want to be. If you want
to change tapes then you don't need much additional
training.
But there is much more to sysadmin than that. The
best sysadmins need just as much technical background
as "programmers" -- they need to understand their system end-to-end, and know how to tune it, change it,
and deploy it.
I know many programmers look down on sysadmins.
But IMHO administration can be just as much a
technical track as programming, and can benefit
from as much background as you can get.
In addition, when I'm hiring sysadmins, what separates "junior" from "senior" folks is their
ability to program. It might be in perl instead
of java/c++/whatever, but I want admins to be able
to automate their day-to-day tasks so they don't have to do things by hand all the time.
This simply isn't true. I downloaded my copy
about a month ago. You have to sign an agreement
and fax it back; you can then download the 200mb
lump-o-stuff at your leisure.
There are two things that control who owns the copyright. The first is the contract. The general rule is that the person writing the code owns the copyright. Employees's writings are owned by the employer. Contractors usually own the copyright unless the contract specifies that it is "work for hire", in which case the client owns it.
The other aspect is that copyright protects expression. Usually machine generated content isn't copyrightable per-se, but the concepts contained within it can be. Object code is protected because it is a automatic translation of the source code. So even though the code was machine generated it might be protected because it captured from an expression of what the screen should look like.
The only downside is the phones they support are not the latest and greatest.
But there is much more to sysadmin than that. The best sysadmins need just as much technical background as "programmers" -- they need to understand their system end-to-end, and know how to tune it, change it, and deploy it.
I know many programmers look down on sysadmins. But IMHO administration can be just as much a technical track as programming, and can benefit from as much background as you can get.
In addition, when I'm hiring sysadmins, what separates "junior" from "senior" folks is their ability to program. It might be in perl instead of java/c++/whatever, but I want admins to be able to automate their day-to-day tasks so they don't have to do things by hand all the time.
This simply isn't true. I downloaded my copy
about a month ago. You have to sign an agreement
and fax it back; you can then download the 200mb
lump-o-stuff at your leisure.
There are two things that control who owns
the copyright. The first is the contract.
The general rule is that the person writing
the code owns the copyright. Employees's
writings are owned by the employer. Contractors
usually own the copyright unless the contract
specifies that it is "work for hire", in which
case the client owns it.
The other aspect is that copyright protects
expression. Usually machine generated content
isn't copyrightable per-se, but the concepts
contained within it can be. Object code is
protected because it is a automatic translation
of the source code. So even though the code
was machine generated it might be protected
because it captured from an expression of
what the screen should look like.
I believe the CA MSN issue was about tying
a rebate to a service agreement; the rebate
had to stand alone and couldn't be conditional.
I know of no problem with having a product
requiring a service agreement (but note that
netpliance allows you to cancel).
A widespread example of this is cell phones.