Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
The Almighty Buck Technology

The Future of SysAdmins' Positions 460

prostoalex writes "With automated upgrade tools and self-updating software, will sysadmins be in such high demand that they enjoy today? Lisa Valentine from NewsFactor provides the answer - and it's a definitive yes. Wireless systems and GPS devices are the new area where sysadmins are expected to have some expertise, although lately companies have been upping their demands for more hands-on experience. This opinion seems to corroborate US Department of Labor forecast on system administrator and computer support specialist employment."
This discussion has been archived. No new comments can be posted.

The Future of SysAdmins' Positions

Comments Filter:
  • Thriving Profession (Score:5, Interesting)

    by mfh ( 56 ) on Wednesday June 09, 2004 @09:02AM (#9376536) Homepage Journal
    Where sysadmins will always thrive is in the ability to connect people who simply don't have time for all the details involved. It's not The Oldest Profession, but it's going to be the longest running profession someday, methinks.
    • by cuzality ( 696718 ) on Wednesday June 09, 2004 @09:04AM (#9376551) Journal
      ...it's going to be the longest running profession someday, methinks...
      The prostitutes aren't going to be happy to hear that...
    • by lukewarmfusion ( 726141 ) on Wednesday June 09, 2004 @09:07AM (#9376574) Homepage Journal
      "It's not The Oldest Profession..."

      Long hours, weekends/holidays, on-call, bad pay... I sure feel like a corporate whore.
      • by Hiro Antagonist ( 310179 ) on Wednesday June 09, 2004 @09:31AM (#9376845) Journal
        I'd mod you up had I points, but I don't so I'll try and post an informative response instead.

        The 'oldest profession' is actually the shaman, or witch-doctor; prostitutes didn't really come around we stopped wandering around so much, and started staying in one place long enough for commerce and property to become tangible things. The witch doctor, like many sysadmins[1], was often insane, but he helped people to make sense of the world around them, by relating things they couldn't understand to things they could -- he was their interface to the unknown.

        Witch-doctors explained disease, thunder, life, death, although they never got the hang of taxes. They were often wrong, not having the tools of science, but their explanations were at least sometimes useful, oftentimes imparted sage advise, and almost always provided comfort to those who sought him for counsel.

        As the world has progressed, so has the witch-doctor; in time, they became 'natural philosophers' and scientists. Today, we call them engineers, doctors, teachers, chemists, and programmers; they are the people that help all of the other people manipulate and comprehend the world.

        They're also called 'sysadmins'; and I'm happy to consider myself a member. *shakes whale-bone and begins chanting*

        [1] Yes, I am one.
        • by gstoddart ( 321705 ) on Wednesday June 09, 2004 @09:45AM (#9376984) Homepage
          Oh, come on. Monkeys barter nookie for food.

          You can bet before we evolved language or shamans some neolithic honey with a single eyebrow and no capacity for language was swapping nookie for food and protection from one of our earliest ancestors.

          Sex goes way back and doesn't require a heck of a lot of cultural evolution to have occured.
          • by chris_mahan ( 256577 ) <chris.mahan@gmail.com> on Wednesday June 09, 2004 @09:49AM (#9377026) Homepage
            She was married?
        • by Profane MuthaFucka ( 574406 ) <busheatskok@gmail.com> on Wednesday June 09, 2004 @10:19AM (#9377386) Homepage Journal
          I thought that was an extremely well thought out article about primitive social practices and professions, and how they link through the ages and are related to the profession of system administrator as it exists today. Most impressive, and it's given me a lot to think about.

          Now, Joe the stupid user installed some spyware on his computer. Go clean it up and be nice: Joe's a vice-president.

          Also, please review the company dress code. You might think yourself a shaman, but some are complaining that you look like one too!

          Kind of puts a perspective on things...
        • by ghostlibrary ( 450718 ) on Wednesday June 09, 2004 @10:36AM (#9377575) Homepage Journal
          Great post. But still, shaman is the 3rd oldest profession.

          0th = (you) = hunter/gatherer
          1st = prostitute
          2nd = spying or politics
          3rd = shaman

          Sort of fits Maslow's pyramid of needs. First you need food, then sex, then safety, then intellectual pursuits. Hunter/gatherer, prostitute/mate, spy/politician, shaman.

          The debate on the 2nd is whether you prefer the Old Testament or Reagon as a source :)
        • This would explain why Bob, our Sysadmin was in our wiring closet whereing a loin cloth, wolf's head hat, and shacking some buffalo bones at my racks of cables. One day I asked him, "What in the hell are you doing in there dressed like that?" and when he stopped his ritualistic dance and song, all of a sudden we were exceeding our collision domain, the UPS's started beeping, our backups were failing, the Internet router failed, and flames were shooting out of the patch panels! Then he looked at me and sai
      • by Lord_Dweomer ( 648696 ) on Wednesday June 09, 2004 @09:35AM (#9376880) Homepage
        I'm sure you'll be disheartened to know that Nevada prostitutes in whore houses get paid about $1000-$2000/hr, don't have to work many hours, and get paid to have lots of sex.

        Methinks many sysadmins would switch professions if only the whore houses would have them.

        • by Syntax Heir ( 725802 ) on Wednesday June 09, 2004 @09:48AM (#9377017)
          Yeah that "whore" thing with all that fancy sex stuff sounds great on the surface but then you have to balance out all the late nights they spend studying to keep up with their ever changing industry.

          Then of course there are the long weekends where they have to work round the clock to fix an emergency!

          Don't forget that everyone is going to expect them to fix problems at home too so their job is extened to the power of N where N = number of employees.

          ...

          HEY! ...

          What a minute! Oooohh.... FWORD!!!!

        • by StormyMonday ( 163372 ) on Wednesday June 09, 2004 @10:36AM (#9377573) Homepage

          No.

          They may *bill* that much, but that's not what they take home.

          You might be surprised at what your company bills *your* time at.

          Also, there's a big difference between "having lots of sex" and "getting fucked a lot." Whores and sysadmins know a lot about the latter.

    • by Wun Hung Lo ( 702718 ) on Wednesday June 09, 2004 @09:07AM (#9376576)
      There will always be positions for competent sysadmins. All the paper MCSE's running around out there might have a problem though. I don't have any respect for a (so-called) sysadmin who pees his pants if you show him a command line.
      • by bonch ( 38532 ) on Wednesday June 09, 2004 @10:50AM (#9377739)
        I don't have any respect for a (so-called) sysadmin who pees his pants if you show him a command line.

        After all, being forced to type in paragraphs of complete gibberish is better than being able to click a checkbox. Your penis size, er, sysadmin skills depend on how many words you type a minute when you administer a network.

        Applying absolutist views to every situation is a copout.
        • Yes, it is better. (Score:4, Insightful)

          by jotaeleemeese ( 303437 ) on Wednesday June 09, 2004 @11:28AM (#9378241) Homepage Journal
          For several reasons:

          How do you script a clicky-clicky solution?

          How do you document it?

          If you dare document it, will it be unambigious?

          With CLI you get all that and more, so it is not a phallic contest but simply the truth and why a UNIX/Linux admin can administer more machines per head than a poor Windows sod.
    • by 59Bassman ( 749855 ) on Wednesday June 09, 2004 @09:11AM (#9376625) Journal
      Somebody's got to be to blame. There seem to be folks in every organization who only exist in case something goes wrong in order to take the beating. If you didn't have a sysadmin, who do you scream at if the e-mail server goes down? Who do you accuse of being inefficient when backups hang up a system for an hour or so? Technology continues to get easier to use, but corporations still need someone with responsibility for that technology.
      • I call this "The Snowden Syndrome," and it's true for Security managers, too.

        If you've never read "Catch-22" by Joseph Heller, there is a character named Snowden. He's a kid who gets shot in a B-25 in WW2. The bombadier (Yossarian) goes back to help him, and when he unzips his jacket, Snowden's guts spill out onto the floor.

        Snowden can't see them, so Yossarian tells him he's going to be alright. He continues to say it until Snowden is dead.

        That is the Security Manager's position to a tee. Their dead
    • Indeed. Especially when you consider the perspective of building systems rather than software installation. As a developer, do I REALLY want to be setting up that new Win2003 server? Or rewiring the network to split it between switches? No! I'm far too busy developing! I'll leave the details of managing hardware, credentials, network routes, system security, virus cleanup (I can't believe my colleagues still manage to get these stupid things), etc. to the SysAdmins. I only want to get involved if there's a
      • by zero_offset ( 200586 ) on Wednesday June 09, 2004 @09:29AM (#9376814) Homepage
        Of course, the flip side of that is that the sysadmins end up with the "keys to the kingdom", and since they're basically janitorial staff, they fail to understand that developers are not just another category of end-users. This becomes more prevalent the larger the company is.
        • by Syntax Heir ( 725802 ) on Wednesday June 09, 2004 @10:17AM (#9377365)
          sysadmins end up with the "keys to the kingdom"

          Agreed

          they're basically janitorial staff

          That's just trolling and entirely unfair.

          I gave the engineering department local admin rights on their PCs before they even asked for it, all I insited on was a 10 minute workstation lockout policy since they love to wander away from their desks.

          However here is a story detailing the problem you mentioned:

          Role Fragmentation [softwarereality.com]

        • by Strange Ranger ( 454494 ) on Wednesday June 09, 2004 @10:55AM (#9377809)
          > they fail to understand that developers are not just another category of end-users.

          [asbestos suit=ON]
          When it comes to securing the network, uptime for people in profit centers, due diligence on things like privacy, data retention, legal compliance, and the ability of the sales team to SELL STUFF for profit...

          developers ARE just another category of end user.

          Profit centers, legal issues, company reputation, shareholders, etc, ALL come before the latest internal Java widget or database enhancement. Sorry, but unless you're developing your company's new flagship product, you'll need to get down off that high horse.
          [asbestos suit=OFF]
        • Oh please. (Score:4, Insightful)

          by jotaeleemeese ( 303437 ) on Wednesday June 09, 2004 @11:35AM (#9378335) Homepage Journal
          Janitorial staff. What is that suppossed to mean?

          SAs normally have a carrier path either laterally (we can become programmers if we want to fro example, we know the resources involved in any IT project which allows to use them more effectively when programming, many programmers just don't understnad how their little script wonder is exhausting all the memory on a given machine) or vertically (toward management, since "having the keys of the kingdom", a position most janitors only dream about, puts you in touch with project managers, business managers, etc. Most code which opens posibilities of progression, code monkeys just code and go home).
  • by destinedforgreatness ( 753788 ) on Wednesday June 09, 2004 @09:03AM (#9376543)
    without sysadmins, who'll deal with the "someone stole the post-it with my password on" queries?
    • without sysadmins, who'll deal with the "someone stole the post-it with my password on" queries?

      That reminds me of a funny one that happened to me. I visited our sysadmin. He gave me a phone number on a post-it. I got done with the phone number and was ready to toss the post-it when I noticed a login and password were written on the back. This was a classic case of a password on a post-it stuck to a computer. It was on the back to hide the password. A sysadmin in a rush to provide a note, grabbed th
  • Yeah, but... (Score:5, Interesting)

    by Mz6 ( 741941 ) * on Wednesday June 09, 2004 @09:05AM (#9376558) Journal
    Did anyone get the feeling the author still knows absolutely nothing about systems administrators after writing this?

    ala... this paragraph...:
    "Many large organizations silo the systems-administration skill set, explains Phillips, and systems administrators at these companies tend to remain focused on very specific systems-administration skills and job responsibilities."

    On a serious note though, I do have a question. The article mentioned that after a few years most college graduates have already achieved sysadmin status, but after that, where do you go from there? The article mentions that the salary tops out at the "mid- to upper-$60,000 range.", and that doesn't sound like a whole lot to me (especially this day in age). Of course there is always becoming a section head, manager, or director... but that often times requires a more downplayed "hand-on" experience as others below you would be doing most of the work. For someone that wants to remain on the technical side of things rather than the business side, where do you go?

    • MBA (Score:5, Interesting)

      by BoomerSooner ( 308737 ) on Wednesday June 09, 2004 @09:09AM (#9376608) Homepage Journal
      You get an MBA, you move into management and become the CIO/CTO. Happens all the time.

      I wish there were a day I didn't have to be the sysadmin at my jobs. Unfortunately I am the default admin because I have the most experience and it's also why I got hired (as a systems developer).

      I admin my own machines as well and the primary reason I like OS X over Linux and Windows is the Software Update. I am evaluating migrating my Linux servers running qmail/oracle/tomcat-apache to OS X Server with postfix/sybase/tomcat-apache.
      • Re:MBA (Score:3, Insightful)

        by micromoog ( 206608 )
        You get an MBA, you move into management and become the CIO/CTO. Happens all the time.

        OK, and what then for the other 90%-99% of the admin staff?

    • Average Salary (Score:3, Interesting)

      by millahtime ( 710421 )
      The mean US household income which is what your average Joe 6 pack makes is about $42,000 a year. If you make $60,000 a year you are about the mean and median US household incomes. There are a lot of educated people making less.
    • Re:Yeah, but... (Score:5, Interesting)

      by duffbeer703 ( 177751 ) on Wednesday June 09, 2004 @09:15AM (#9376659)
      Nowhere.

      The notion that you career as a programmer or technical specialist is going to plateau before you hit your 30's is scary, but often true.

      You can make more money in sales, consulting or management. But there are tradeoffs. If you want to be a high-dollar consultant or salesman, the travel can really kill a marriage. If you become a management dork, you essentially abandon your technical career.

      The "where do you go?" question is something facing all middle-class people. Over the last 40 years, the purchasing power of the average person has eroded sharply.

      My grandfather raised a family of six on one blue-collar income, and managed to own a nice home in NYC, a summer house upstate, and always had two cars. Good luck doing that today.

      • Re:Yeah, but... (Score:3, Insightful)

        Except for the two homes and family of six, I am planning on doing that by not wasting my money burning dinosaurs. I plan on building an energy efficient home (which are very cheap to build, depending on the materials you use; straw bales make excellent walls) and driving energy efficient cars. I'm also going to make sure my kids spend more time outside than in front of the TV so that they're not exposed to the corporate consumption mindfuck that children's TV is. My ideal would be if they ask for books for
    • Re:Yeah, but... (Score:5, Informative)

      by raddan ( 519638 ) on Wednesday June 09, 2004 @09:15AM (#9376666)
      For someone that wants to remain on the technical side of things rather than the business side, where do you go?

      Back to school, for ECE. It will kinda suck to be an undergrad all over again, but I'd like to think that I have a bit more focus this time around.

      Being a systems administrator is neat with regard to some things; there's a lot of equipment I wouldn't have ordinarily gotten my hands on, a lot of problems I wouldn't have ordinarily confronted. But there's not much thinking to the job and I feel a little starved for a challenge...

    • Where you go next (Score:5, Insightful)

      by Wingchild ( 212447 ) <brian.kern@gmail.com> on Wednesday June 09, 2004 @10:28AM (#9377488)
      Try the government and/or the military.

      No, really; as an independant contractor.

      One of the interesting things about working as a defense contrator is that there is work everywhere in the world at present; doesn't matter where, we've got an investment, and that investment involves computers somewhere along the line. (Yes, even in Kuala Lumpor - even when it's disguised as France.)

      Where there are computers there will be admins - there must always be admins - if only for the same reasons that there are doctors, lawyers, mechanics, and others of our ilk. On the whole it's stuff that reasonable people could figure out and generally take care of on their own. Sometimes they'd need a specialist for a particularly hairy problem. However, one of the defining traits of life is that people don't have time to be generalists -- we're a highly specialized society (even if some of those specialties are along the lines of the service industries). Admins exist to take care of what people can't or won't, and in theory to do a better job than they could without training.

      This is doubly or triply true for the government and military. More amusing still is if you're doing defense work that requires a clearance. If you can find someone to sponsor you, and if you can pass the investigation (takes a semi boring life, or lots of honesty), by all means do. Most people who go for a clearance won't get one - or will eventually have it revoked.

      Law of supply and demand, friends:

      High demand + automatically limited supply = higher cost for the goods in question. (i.e., higher salary.)

      Get your Top Secret and you've basically written your meal ticket for life; just lay off committing felony crimes and you're probably good to go. :)
    • $60,000? (Score:3, Insightful)

      by uslinux.net ( 152591 )
      Really? Don't tell my boss that.
  • Jobs (Score:5, Insightful)

    by thebra ( 707939 ) * on Wednesday June 09, 2004 @09:06AM (#9376568) Homepage Journal
    There will always be jobs for persons in IT that are willing to learn new technology as it changes daily. There will always be a job for position "X" as it will change as technology changes.
  • by tcopeland ( 32225 ) * <tom@NoSPaM.thomasleecopeland.com> on Wednesday June 09, 2004 @09:07AM (#9376572) Homepage
    > An experienced systems administrator
    > can expect to earn a salary in the
    > US$50,000 to mid- to upper-$60,000 range.

    Hm, the _average_ in the SAGE survey [sage.org] in 2002 was $67,600. But I guess that's more or less in the ballpark.
  • I thought (Score:5, Funny)

    by Prince Vegeta SSJ4 ( 718736 ) on Wednesday June 09, 2004 @09:07AM (#9376575)
    that with pay cuts, job cutbacks, the dot-bomb, and outsourcing.

    Admins have been forced to "Assume the position" for quite some time.

  • Experience (Score:5, Insightful)

    by the Man in Black ( 102634 ) <jasonrashaad@@@gmail...com> on Wednesday June 09, 2004 @09:07AM (#9376581) Homepage
    Wireless systems and GPS devices are the new area where sysadmins are expected to have some expertise, although lately companies have been upping their demands for more hands-on experience.

    Which is fine for currently employed sysadmins, or more specifically currently employed sysadmins that have the rare opportunity to do research and put their hands on new technologies in addition to their day-to-day tasks. However, the majority of us (my experience, no empirical evidence) is that most of us are hired to do a specific task, or hired to handle a certain area. Then 90% of our time is eating up just keeping the walls from falling down, making it difficult to get up to speed on new technologies.

    How are we supposed to get this high-demand experience if we're either busy doing our jobs or still looking (or both)? They don't exactly teach sysadmin in school, you know.
    • Re:Experience (Score:5, Insightful)

      by Moderation abuser ( 184013 ) on Wednesday June 09, 2004 @09:16AM (#9376679)
      "Then 90% of our time is eating up just keeping the walls from falling down"

      If 90% of your time is spent fighting fires, there's something fundamentally wrong with the way the systems are set up or you're chronically understaffed. Now, I can scale *myself* from 100 to 1000 systems with little additional effort on my behalf once they are set up.

      "They don't exactly teach sysadmin in school, you know."

      True, you have to teach yourself. http://www.infrastructures.org/

  • by Moderation abuser ( 184013 ) on Wednesday June 09, 2004 @09:07AM (#9376583)
    Yeah. Until something breaks that is.

    In general I see my job to automate everything I can. Repetitive work is what computers are good at, get them to do it for you. The sysadmin will still be required to oversee it.

  • by Slick_Snake ( 693760 ) on Wednesday June 09, 2004 @09:08AM (#9376588) Journal
    Even with automated updates and other utilities it still will take someone with some brains to fix problems that are more than just installing the latest patches. Any moron can install a patch.
  • by Anonymous Coward on Wednesday June 09, 2004 @09:09AM (#9376609)
    There is no system that can provide the level of personally tailored abuse that I offer users on our network. Most users are masochists -- they don't just want to be told they're doing something stupid, they want their intelligence to be abuse for it. Honestly. At least that's always been my philosophy...
  • *sigh* (Score:4, Interesting)

    by lukewarmfusion ( 726141 ) on Wednesday June 09, 2004 @09:10AM (#9376617) Homepage Journal
    Sysadmins will always be needed because technology doesn't stand still. Ten years ago, a sysadmin was responsible for different systems, different technologies, and different processes. Add in wireless, PDAs, GPS, etc. and you see the point - new tech means new things to learn, new responsibilities, and that much more job security.
  • by nurb432 ( 527695 ) on Wednesday June 09, 2004 @09:11AM (#9376624) Homepage Journal
    Unless unforeseen technologies appear over the horizon that are overly complex, this is only a short term thing. ( notice how most new technologies today are simplistic to the end user )

    In time, things become either 'user managed' or 'self managing' ( and cheap enough to throw away when it breaks ) and most of the need of a real admin ( or service tech, programmer, etc ) goes out the window

    Sure there will be a few left, but most techies will be in the soup line. Especially the older ones with experience that costs a lot.

    Face it, the IT industry is going to pot, if you work in it. If you are user, its booming.. Cheaper stuff, and less expensive support needed..
    • You have obviously never been a system administrator. Allow me to introduce you to my friend, Clue-by-Four.

      *whack*

      The problem with things that are 'user-managed' is that it follows the classic path of the tragedy of the commons. Users tend to look at the systems and networks they use as infinite sources of storage, memory, and processing power, and when things break down because of this overuse, they have no way to fix things on their own.

      The place I work is a great example of this -- our salespeople h
  • by conJunk ( 779958 ) on Wednesday June 09, 2004 @09:11AM (#9376628)
    it's an interesting article, and it's dead-on about predections, but i think for the wrong reasons

    sure, a lot of what we used to do is automated (as the article points out, software installs, etc.), but a lot of what we do is purely psychological

    i doubt there is PHB anywhere that is so braindead to think that his human sys admin slave (who can receive a page at 3 am) can be replaced by a machine

    nobody is so daft as to imagine that our work is anything but intellectual... they watch as at work, at front of the machine, and they know that what we are doing is no different that auto mechanics or detectiving or archaelogy... analytic problem solving employing a specific skill-set, and there's no machine that can do that, and upper management (thank god) knows it

    until they invent a computer that can drive down to the co-lo in the wee hours and apply critical thought to packet-sniffer, humans will always be sys admins, and the article doesn't touch this part of it
  • by spidergoat2 ( 715962 ) on Wednesday June 09, 2004 @09:13AM (#9376649) Journal
    I'm not trying to Microsoft bash, but as long as Microsoft controls the desktop and server market, and as long as there are software vendors that ignore programming guidelines, there will always be a need for admins. I get calls all the time from users trying to figure out how things are supposed to work. I find most problems easy, yet the users are baffled. That, combined with the constant threat of virus, hacker and spyware attacks, makes me confidant I'll be employed for a long time to come. Unless I waste too much time on /.
  • by GillBates0 ( 664202 ) on Wednesday June 09, 2004 @09:14AM (#9376656) Homepage Journal
    With automated upgrade tools and self-updating software, will sysadmins be in such high demand that they enjoy today? Wireless systems and GPS devices are the new area where sysadmins are expected to have some expertise, although lately companies have been upping their demands for more hands-on experience.

    Looks like Miss Valentine here missed a crucial reason - increasing software complexity and bloat. Wireless/GPS and other cutting technology is all fine and dandy, but even traditional systems (read OS's, Source Control, Systems Software, Clusters) have been getting more and more bloated, complex and difficult to manage over the past few years.

    As software developers continue to add more and more features/bugs to systems, the amount of effort required to keep the system up and running grows exponentially. I know a slew of companies which have admins/groups dedicated to simply keep Source Control systems running smoothly so actual software developers can get some work done. So to summarize...until we can come up with truly self maintaining/repairing software/hardware, people will be required to administer/manage those systems.

  • Still Needed... (Score:3, Interesting)

    by NetJunkie ( 56134 ) <jason.nash@nosPam.gmail.com> on Wednesday June 09, 2004 @09:15AM (#9376661)
    This topic comes up every so often. I can honestly say my workload hasn't decreased one bit even with easier to manage systems. Expectations continue to increase and new technologies are implemented. Over the last year or two we've seen a huge surge in wireless deployments, as one example.
  • Well, duh! (Score:3, Insightful)

    by smoon ( 16873 ) on Wednesday June 09, 2004 @09:20AM (#9376722) Homepage
    Of course sysadmins are going to be in strong demand. Automated systems can only do so much, someone has to fix things when they break down, and the workload keeps increasing.

    This isn't unlike a fighter pilot who has too much to think about. Innovations like a heads-up-display and fly-by-wire don't make their job easier -- it just allows for more things to get done.

    The complexity of a typical corporate network is absolutely mind boggling, and it is completely unrealistic to suppose that automated systems are going to 'self heal'. Someone has to understand what's going on and how to add and modify things.

  • Catch 22 (Score:3, Insightful)

    by WarriorPoet42 ( 762455 ) <{moc.hcet-nosbig} {ta} {kcin}> on Wednesday June 09, 2004 @09:22AM (#9376743) Journal
    The problem for some is becomming a sys admin. Most sys admin want years of hands-on, but to get years of hand-on you first have to get a sys admin job, but to get the job, you first need years of hands-on . . .
    • Re:Catch 22 (Score:3, Insightful)

      by dknight ( 202308 )
      I was in a very similar boat. I found the solution to be kinda sneaking in the backdoor. I went into a non-sysadmin related position. I became a VTC engineer. Well guess what? VTC groups have servers. Lots of em.

      And hey, they dont have any tech guys. What in the world were they planning on doing? So guess what? Now I'm a systems administrator. Its on my resume, and I'm IN!
  • by More Trouble ( 211162 ) on Wednesday June 09, 2004 @09:23AM (#9376750)
    With this newfound time, systems administrators are taking on responsibility for additional technologies, such as security and wireless.


    Newfound time? This is the time that is now available because there are no more worms or viruses and/or Windows has become impervious to them. Check.

    :w

  • Comment removed (Score:3, Insightful)

    by account_deleted ( 4530225 ) on Wednesday June 09, 2004 @09:25AM (#9376772)
    Comment removed based on user account deletion
  • by Pollux ( 102520 ) <speter@[ ]ata.net.eg ['ted' in gap]> on Wednesday June 09, 2004 @09:28AM (#9376798) Journal
    With automated upgrade tools and self-updating software, will sysadmins be in such high demand that they enjoy today"

    Oh brother. Alright, let's look at the history of cars:

    Before ~1970: cars had: engine, manual transmission, radiator, distributor, carborator, master cylinder.

    Everything was mechanical (excluding battery / ignition system). So, you took your car to a garage, the person who worked on the viechle was a mechanic. These guys were skilled at knowing how moving parts all worked together to make your car go.

    After ~1990: cars have: engine, auto transmission, radiator, automatic distribution system, fuel injection, anti-lock breaking system, power steering...there's a lot more things that are electronically controled and regulated. But guess what? These things still break. We still have mechanics, because there are still a lot of things that are mechanical, but there are also "technicians" (and most mechanics have to be technicians as well) that know how to fix electronics. Even if the "systems" are more reliable than before, they still break. But at the same time, my radiator worked exactly like radiators 50 years ago.

    Add more "systems" to computers, it's just more "systems" that admins have to administer to when they break.
  • by gillbates ( 106458 ) on Wednesday June 09, 2004 @09:36AM (#9376883) Homepage Journal
    There will be a need for sysadmins...
  • by EmagGeek ( 574360 ) on Wednesday June 09, 2004 @09:39AM (#9376913) Journal
    We got rid of all of our sysa&%$#IU@Hm years ago... we have no$&Y@U problems to speak of in our net84(*#&$@.. .NO CARRIER

    CONNECT

    sure there's a glithIUEY#$ now and again, but for the most part, things run very smoot83Y(*$@Y#$NO CARRIER
  • by boxless ( 35756 ) on Wednesday June 09, 2004 @09:39AM (#9376917)
    I used to worry about this, but I don't any more.

    I've been doing this shit for 14 years, and in that time, even with GUIs and Plug-and-Play, and DHCP, and all the other niceties, in sum total, the complexity I face has increased year over year, not decreased.

    Of course, the technology has gotten easier to install and maintain, but there's a lot more of it now, and it has infiltrated all aspects of the business world to where it really is counted on more than it once was.

    I just didn't see that level of dependency 14 years ago.
  • by RabidMonkey ( 30447 ) <canadaboy.gmail@com> on Wednesday June 09, 2004 @09:40AM (#9376919) Homepage
    As a systems admin with 5 years experience currently working on a helpdesk to make ends meet, I'd like to ask, where is this glut of jobs that the poster implies is out there? I know in the Toronto area, there are quite a few out of work sys admins and any job I find gets 100's of applications.

    Things aren't so peachy keen here in sys admin land ...
  • by jdfox ( 74524 ) on Wednesday June 09, 2004 @09:40AM (#9376933)
    [spoken]
    I never really wanted to be a scientist.
    I wanted to be...a...a SYSADMIN!

    [system engineer choir and shift supervisor enter, music strikes up]

    Oh, I'm a sysadmin and I'm OK,
    I grep all night and I chown all day.

    [choir]
    He's a sysadmin and he's OK,
    He greps all night and he chowns all day.

    I ping the nodes, I do PM,
    I awk and perl and sed.
    I've got a Star Wars lunchbox,
    And Tron sheets on my bed!

    [choir]
    He pings the nodes, he does PM,
    He awks and perls and seds.
    He's got a Star Wars lunchbox,
    And Tron sheets on his bed!

    I ping the nodes, I change the rates,
    I fork the processes.
    I wish that all my lusers
    would catch some rare disease!

    [choir, growing slightly uncomfortable]
    He pings the nodes, he changes rates,
    He forks the processes.
    He wishes all his lusers
    would catch some rare disease!

    [choir brightens as they repeat chorus]

    I ping the nodes, I lock the /home partition and umount.
    I post .gifs of my boss's daughter from his own account!

    [choir]
    He pings the nodes, he locks the /home partition and umounts??

    [shift supervisor, in tears]
    Oh Bevis! And I thought you were so dedicated.

    (quoted from Martin Martin "I wish to register a complaint about this system" Booda)

  • by l33t-gu3lph1t3 ( 567059 ) <`moc.liamtoh' `ta' `61legna_hcra'> on Wednesday June 09, 2004 @09:42AM (#9376949) Homepage
    If sysadmins are/will always be in high demand, why did Humber College (biggest tech college in Ontario) just fold its Information Technology Studies department, orphaning all its current students? Why is own Bachelor of Applied Computing program at the University of Guelph-Humber barely able to generate enough interest to get half of a full class admissions for 2004-2005 academic year?

    While there may be demand and a decent marketplace for sysadmins, there sure as hell isn't interest in the field for the kids entering post-secondary.
  • by chegosaurus ( 98703 ) on Wednesday June 09, 2004 @09:44AM (#9376975) Homepage
    Haven't sys-admins always spent half their time automating things? When vendors didn't supply automated patch tools, we made our own. When our companies wouldn't buy backup or monitoring tools, we made little makeshift ones ourselves.

    Increasing complexity means these kinds of tools allow us get our jobs done. Without them we'd be buried in work, with them we can deal with the 1001 jobs that can't be automated.

    Now, admins writing scripts to replace other people... that's a different matter.
  • Whaaa? (Score:3, Funny)

    by The Ape With No Name ( 213531 ) on Wednesday June 09, 2004 @09:51AM (#9377051) Homepage
    automated upgrade tools and self-updating software

    Yes, that wonderful all-knowing all-seeing demiurge that M$ fanboys claim is the fault of the user!
  • Offshoring? (Score:3, Interesting)

    by jjjefff ( 525754 ) on Wednesday June 09, 2004 @09:54AM (#9377089) Homepage
    What about offshoring? It's a big concern for others in the tech fields, but doesn't seem to get mentioned that much in sysadmin discussions. Yet, I worked for five months as a sysadmin for a ~10-machine development environment in Toronto, Canada, and never left Austin, Texas. I just had a physical resource I could call there and say, "Go reset this box," or "On Saturday morning, we're going to replace so-and-so ethernet controller." So, I'm not India or Russia, but I did a pretty good job maintaining an environment from a thousand miles away...
  • by martin ( 1336 ) <`moc.liamg' `ta' `cesxam'> on Wednesday June 09, 2004 @09:58AM (#9377125) Journal
    and look what a sorry state most Windows installations are like.

    put in once by the bosses PFY and nevert touched again.

    make no wonder there's a massive proliferation of malware.....

    IMHO
    Your computer systems are like a car and should be be regularly maintained/serviced like a car or they will let you down..

  • by rsletten ( 98901 ) on Wednesday June 09, 2004 @10:00AM (#9377141)
    *clickety-clik* you have lots of space now.
  • by Ektanoor ( 9949 ) on Wednesday June 09, 2004 @10:40AM (#9377621) Journal
    ... if the current state of affairs will keep on.

    For the last years anyone at the front line of techsupport, network and system administration has seen how the user "community" gets dumbier and dumbier. Recently we had a very good laugh after one guy bought an Internet account, not having a computer anywhere...

    Soom we will see Internet reaching consumer electronics and mobile phones... When this comes up, things will be even worser...

    However, if sysadmins will think this is a good prospect for a "new" boom and good salaries... Well, sorry people. Most of the sysadmin mass will be also dumb lusers with shiny suits and mostly empty pockets. Frankly, the wholescale tendency is to turn us into a Paleontogical exhibit. No one will succeed on this, but the "market" environment created by Microsoft will still prevail for years. No matter the policy "sysadmins wouldn't be needed", they will be in place, mostly as janitors, mechanics and tubing rats...

    This will keep on until something wakes up everyone... And people die or highly suffer with it...

    Then... Well... It is hard to predict what may happen on a "day after"... But maybe we will see better times... Or maybe we will see something much worser...

    Until then, there will be a few pockets of Digital Life where some hardskin sysadmins, developers and hackers will keep going on serious stuff...
  • by ConceptJunkie ( 24823 ) on Wednesday June 09, 2004 @11:18AM (#9378124) Homepage Journal
    What radical transformation is server hardware and software undergoing that makes anyone think this stuff will suddenly work so well that it will reduce the need for experts to maintain and operate them? Heck, the mere existence of Microsoft guarantees lifetime employment for anyone willing to suffer though learning how to use their software, and this is exacerbated by the fact that Microsoft seems to be exceeding Moore's Law (but in terms of code size and complexity) while delivering at best, a slow linear increase in real functionality.

    Short of AI, I don't see sysadmins ever going away, or even decreasing.

  • by GPLDAN ( 732269 ) on Wednesday June 09, 2004 @11:20AM (#9378139)
    I've read all the 3+ posts here. So far, nobody has mentioned a really important fact.

    because the skillsets in demand are always shifting, and because HR people really want to check off boxes in their application interviews, you get obsolete very fast. As you move into your 30s and 40s and beyond, your skill set is NOT like a lawyer's or doctor's. Their experiences over time make them stronger and stronger, and more valuable to society. You become LESS so. While a lawyer needs to learn about new laws and changes to the system, the rate of change doesn't invalidate what they already know.

    Our company just laid off 10 people who were 50-ish COBOL programmers and IBM sysadmins. These people were very good at what they did, but they were no longer needed. They now start sliding DOWN the chain, taking jobs in their fields for LESS money. No matter how smart you think you are, there are college grads who will fight you for your job and take half your pay.

    A previous poster compared sysadmins to auto mechanics. That was a good analogy, but he didn't follow it through. What happened to the mechanic industry in the 80s and 90s? They stagnated or dropped, as existing mechanics found it harder and harder to adapt to all the new technology, the demographic shift in average mechanic age fell.

    I don't mean to be doom and gloom here, but for those who won't go into management or strike out and become busines owners, the future is this: you MUST stay on top of all emerging technologies and keep certifying and run along the treadmill, or you WILL get replaced by somebody younger. Whatever guru status you think you enjoy, and however many times your manager calls you his "goto guy", that status changes OVERNIGHT.

    You should look at the sysadmin field like playing MLB in your 20s and early 30s. It's great to make it there, and it helps you make money you wouldn't have otherwise made - but eventually you will be replaced by somebody better and faster and cheaper. You need a plan to do something outside the field after 40.

    Quick aside, I looked at some job ads in the last few weeks. I think HR people haven't figured out that some of these ads are stupid, and the economy is picking up and they can't cherry pick quite so much. I saw an ad that the company wanted you to have 10+ of systems integration experience, consulting experience, have technical certifications like RHCE and know shell, programming in C++, Java and be a certified disaster recovery specialist - AND - you know, in your spare time, ALSO be a CPA. That's right, a CPA!

    Now maybe I just don't know enough smart people, but so far I have yet to meet a CPA that is also a programmer, much less a highly experienced sysadmin. I don't even know any that can SPELL UNIX. I would REALLY love to meet the applicant that gets that job.

  • by ErichTheRed ( 39327 ) on Wednesday June 09, 2004 @12:10PM (#9378839)

    Sysadmin jobs for smart people who know a wide range of systems will still be around. However, expect some changes, including the following:

    • Very few sysadmins can afford to be the geek hiding behind the server racks. You'll be expected to interact with users, understand their needs and generally function as part of the business. If you're the _one guy_ who knows absolutely everything about the main system that your company uses to make its money, then you're the exception. Otherwise, those social skills are going to come in handy!
    • The outsourcing thing is going to hurt for the forseeable future. If your job doesn't get sent overseas, it's pretty likely that permanent IT staff positions will be transferred to third parties. This leads to wage compression as the outsourcer tries to squeeze every last profit dollar out of their deals.
    • Knowing one OS isn't going to cut it anymore. I'm a Windows sysadmin by trade, but know Linux relatively well (the problem is getting into a Linux shop after working in Microsoft shops...I swear I must have a big red "M" tattooed to my forehead. :-)
    • The days of the paper MCSE are numbered, and it's a small number. Lots of Microsoft sysadmins aren't bothering to learn things like scripting, task automation, etc. that are essential on every other platform in the world. That's what separates the paper MCSE from the qualified windows admins.
    • There's very little opportunity to "break in" like there was in the 90s. IT employers are becoming much more impatient with new hire ramp-up time, and it's getting harder to find entry-level IT work that doesn't involve fixing computers at Best Buy.

    Back in the day, systems were extremely complex and needed an army of people to look after the basic functionality. Now that's changing...sysadmins will be around, but adaptation is required.

    The other thing that I see happening is formation of a common set of procedures. Civil engineers rarely design faulty bridges, airports, train stations, etc. The reason is that they use tested methods, and "new cool stuff" goes through complete peer review before becoming generally accepted. Systems people, OTOH, build stuff that routinely crashes and fails to work as advertised. Once companies get out of the "outsource everything and pay the absolute minimum for the work" phase, I think it will be time to form a real governing body similar to the professional engineering organizations.

    • Back in the day, systems were extremely complex and needed an army of people to look after the basic functionality. Now that's changing...sysadmins will be around, but adaptation is required.

      Back in the day? What gets MSCE's into trouble is that systems ARE that complicated, and will continue to be that complicated, and that their training was inadaquate for managing all but the simplest Windows network.

      Last I checked a decent admin had to have a working knowledge of TCP/IP, routing, and the myriad supp

  • by wintermute42 ( 710554 ) on Wednesday June 09, 2004 @01:04PM (#9379506) Homepage

    Increasingly we are seeing the executive branch (e.g., the departments that report to the President) either not publish statistics or publish misleading or partial statistics. This is true for many departments that previously prided themselves on non-partisanship.

    The job forecasts and market outlook for programmers and software engineers did not mention anything about outsourcing. Could this be because outsourcing is a senstive political topic that the current administration is vulnerable on? I found it odd reading that job growth for programmers would be about the same as job growth overall, without any mention of why such tepid job prospects were being forecast. In fact, I found nothing about low wage competition for "knowledge worker" jobs.

    Then there is the issue of job catagories. Apparently the job prospects for "software engineers" were bright, while those for programmers were mediocre.

    I have never worked in an environment where someone did design and someone else implemented this design in software. Yes I've had customers provide a broad outline of what they wanted, sometimes in terms of system components, but the engineering of large software systems is closely tied to their implementation. So as far as I'm concerned the division between "programmer" and "software engineer" does not exist. In fact some of the problems encountered in offshore outsourcing involve the attempt to separate software engineering from programming. Those contracting for low wage programming must provide detailed documentation that describes exactly what they want and how they want it done. Even then sometimes the software that is delivered is not adequate.

  • by kidlinux ( 2550 ) <.duke. .at. .spacebox.net.> on Wednesday June 09, 2004 @04:56PM (#9382089) Homepage
    Sysadmins will always be around because someone has to setup that automated software. If it actually got to the point where "automated" software ran smoothly 99% of the time, then the sysadmin might work for (or be) a contractor who comes in when things break. That person is still a sysadmin. If the sysadmin were in-house then his role might diversify and cover more duties - programming, administration (of the non-system type), management. The sysadmin may even be doing stuff not related to computers.

    Whatever happens, the sysadmin will still be necessary.

"The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts." -- Bertrand Russell

Working...