Slashdot Mirror


What an IT Career Will Look Like 5 Years Out

snydeq writes: InfoWorld's Paul Heltzel reports on the impact that IT's increasing reliance on the cloud for IT infrastructure will have on your career in the years ahead. "[O]ne fact is clear: Organizations of all stripes are increasingly moving IT infrastructure to the cloud. In fact, most IT pros who've pulled all-nighters, swapping in hard drives or upgrading systems while co-workers slept, probably won't recognize their offices' IT architecture — or the lack thereof — in five years. This shift will have a broad impact on IT's role in the future — how departments are structured (or broken up), who sets the technical vision (or follows it), and which skills rise to prominence (or fall away almost entirely)."

31 of 233 comments (clear)

  1. Career Is But A Quait Concept Now by damn_registrars · · Score: 5, Insightful

    Careers, at least as we used to know them, are mostly gone now. We won't see them again any time soon. Even the industry that the federal government so lovingly bailed out back in 2010 has been laying off plenty of IT workers in recent times, and they were amongst the most stable places for IT "careers" before now. If you want to be able to retire at some point before you die, you need to be constantly looking for other job opportunities. Move up, move down, move laterally; it doesn't matter. Just keep moving or you'll be under the chopping block.

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    1. Re:Career Is But A Quait Concept Now by Anon-Admin · · Score: 4, Informative

      This is an IT Management issue that I am hoping someone will realize is a huge drain on the budget.

      1) New IT manager arrives with vision of how he is going to improve IT
      2) Hires new staff to realize that vision
      3) Trains new staff. ($$$)
      4) Is promoted in 2 to 3 years into a new higher position.
      5) New IT Manager arrives with new vision of how he is going to improve IT
      6) Decides the company needs "New Blood" in IT and proceeds to lay off old IT staff.
      7) Hires new staff to realize that vision (In most cases paying %10-%30 more to get new staff due to salary changes over the years)
      8) Trains new staff. ($$$)
      9) Is promoted in 2 to 3 years into a new higher position.
      10) Rinse and Repeat.

      Each round you loose the knowledge of what was tried, and failed, before and what worked for the business need. I have seen new managers come into a company and decide to revamp the whole system with no review of ROI, TCO, or even the understanding that completely retooling the environment will be cost prohibitive.

    2. Re:Career Is But A Quait Concept Now by Ol+Olsoc · · Score: 2

      10) Rinse and Repeat.

      This is very similar to the in-house versus oursource issue. Our's was on a five year cycle. Engineers on one side, bean counters on the other.

      A;ways came back to in house because of the control, then the bean counters show how much money can be saved by outsourcing, then all that money saved and more is wasted by reworks and travel, then it comes back in house for the control, then the bean counters show how much money can be saved......

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    3. Re:Career Is But A Quait Concept Now by rayd75 · · Score: 4, Interesting

      Wow. That is possibly the dumbest thing I have read on here. Keep moving, or you will get fired? Who is going to hire someone who keeps switching jobs constantly? I'm sure you will be modded to +5 Insightful though.

      I've been interviewing candidates for a high-end generalist position for six months now. (We're cheap and no-name) One thing that has struck me is that few people stay at an IT job for more than 18 months to 2 years. I'm an exception, having been here for 7 years and at my previous job for 9. But what really surprises me is that I've started to consider those 18 month stints as normal. Now, when I look at a resume where someone has been at the same place for 3 or 4 years, I ask myself "What's wrong with this person that they couldn't find another job?" It never crosses my mind that they, like me, might simply have found a relaxed environment in which they're comfortable and not expected to hold down a desk for 9 hours before doing the real work after everyone else goes home. It's scary. I'm both the senior technical person at my organization and my IT department's hiring manager... and by my own standards, I'm practically unhirable.

  2. Bonus Impact by phmadore · · Score: 4, Insightful

    Whole organizations will be reliant on whole other organizations, who may go out of business on the random, or get swallowed up by competitors of whole organizations(1).

    1. Re:Bonus Impact by Anonymous Coward · · Score: 3, Funny

      But think of the short term savings!

  3. And in most cases it is wrong by rtkluttz · · Score: 5, Insightful

    In reality a hosted cloud is more expensive and less secure in almost all cases. When will people wake up and realize that cloud was created not to provide any particular service that can't be provided locally, but is just a way to turn something you used to pay for once into a monthly forever and ever payment. Cloud is cheaper up front, but almost always more expensive in duration.

    --
    Digital is, by definition, imperfect. Analog is the way to go.
    1. Re:And in most cases it is wrong by mccalli · · Score: 2

      "a way to turn something you used to pay for once into a monthly forever and ever payment"

      Not necessarily, no. If I buy my own kit, I need to care about support contracts for that kit, end of life status for that kit, upgrades, system design for (infrastructure-level) uptime etc.. If I use a cloud service (I hate the word, but it's stuck so there we go) then I don't need to do that.

      It's trade-off. Cloud is not all good, but it's not all bad either. A lot of gardening-style detail of looking after kit goes away, but clearly there are still things you need to worry about.

    2. Re:And in most cases it is wrong by coofercat · · Score: 5, Insightful

      From a business point of view, using the cloud means you get to put your monthly costs into your "op-ex" as opposed to buying a load of stuff up front (with cash) and writing it off over a couple of years on your "cap-ex". That can help your accounts look good because you get to maintain cash flow (particularly in the early days) and don't have lots of assets on the books. Not one single accountant that looks at your accounts will know if you're getting a good deal from your cloud or not, so it's works very well at impressing those sorts of people. Those sorts of people are quite probably your backers and bankers, who are increasingly risk adverse. They don't want to give you loads of cash today which all gets spent immediately (on the promise of success) and so would much rather drip-feed out their investment in you over a couple of years as they see success actually happening.

      Going to the cloud means you don't need start-up capital to get started. In that sense it's very good and a great enabler of small business. However, as you say, once you've started up, you're better off taking the initial hit (from your cash reserve) to buy it all and run it in house. If you've got any sort of reputation to maintain, then moving stuff in-house is pretty much your duty of care (well, it is as soon as you lose your data and your customers complain about it). The question is... when are you no longer a "small business" that can be forgiven minor transgressions and "big enough" that you should know better? It seems to me that lots of really big corps. are trying to pretend they're "small" (ie. lean start-ups) when they absolutely should know better. We'll probably have to ride this out until the next 'fad' comes along.

    3. Re:And in most cases it is wrong by gmack · · Score: 2

      It is a tradeoff that often works in favor of the cloud for smaller companies. Here, we did the math and discovered that at $5 an email, the yearly cost was higher than my new mail cluster+ 9 TB san we already deployed and that math was still working against the cloud when we applied the resulting proposed discount.

    4. Re:And in most cases it is wrong by Jawnn · · Score: 3, Insightful

      Well said, sir. I would only add that regulatory compliance also makes "going to the cloud" more complex and expensive. Despite their claims, most cloud vendors claiming to have "compliant" solutions, have a poor understanding of the regulations their claiming to comply with. Not saying that their aren't vendors who do it right, but from what I've seen, using something from that group is definitely more expensive than doing it in-house.

  4. We're still trusting the cloud? by geekmux · · Score: 3

    Seriously?

    Wonder how many more times we're going to hear of cloud architectures being compromised before that idiotic mentality changes.

    1. Re:We're still trusting the cloud? by l3v1 · · Score: 4, Insightful

      Problem is, when a company's own infrastructure gets compromised, they get fsckd, but when a 'cloud' provider gets compromised, everyone they host get fsckd.

      --
      I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
    2. Re:We're still trusting the cloud? by lgw · · Score: 2

      That's not a problem, that's somebody else's fault, which is the first thing and CIO looks for in any solution.

      Though, really, have we ever seen the clouds from Amazon, Google, or Microsoft get compromised?

      --
      Socialism: a lie told by totalitarians and believed by fools.
    3. Re:We're still trusting the cloud? by lgw · · Score: 2

      The NSA has everything compromised, though, so that doesn't differentiate cloud from non-cloud. That's very different from, say, the Sony hack, where everything becomes public.

      --
      Socialism: a lie told by totalitarians and believed by fools.
  5. Not really. by magamiako1 · · Score: 4, Insightful

    People keep saying this to me. "Oh we won't need your type in a few years because cloud everything." Never mind the fact that around 99% of my work is software-based. I only rarely on occasion mess with hardware. Every 5 years for a hardware refresh, and the occasional drive swap from a vendor. Everything else I do is software-based. And it really doesn't matter whether it's "in the cloud", or "on premise". My job role stays the same. So I save a whole 15 minutes a year on not having to swap drives.

    What you will see with "cloud", just like "virtualization", is a maturation of the technology's use inside a company. Not every workload is appropriate for virtualization, and not every workload will be appropriate nor cost effective in the cloud. The cloud is great for every "devops" guy who thinks they're going to write the next Facebook, Amazon, or Netflix--but yet again, for 99% of companies out there, workloads are entirely static. There's just little need for "SUPER HYPER SCALE AUTOSCALING UP AND DOWN CLOUD INFRASTRUCTURE" for a vast majority of business workloads.

    Specific applications are hugely appropriate for "cloud", particularly e-mail (and I say this as an Exchange Administrator). And for these "we need this up 110% of the time" applications, they'll find that if the "cloud vendor" has a problem there's nobody they can call to fix the issue. And never underestimate the value of management having someone that they can call to "look at the issue right away at 2:30AM". This need will keep a lot of folks employed.

    Finally, you can't really depreciate cloud assets like you can capital expenses. So really, again, you're ultimately just comparing the cost of operating a datacenter versus the cloud technology. And you can already not worry about operating your own datacenter by simply using a colocated one.

    So at the end of the day, no matter how much technology changes. No, the 'devops' revolution isn't actually going to happen, and being able to swap a drive or add some ram will still be a necessary skill.

  6. And there will be no mainframes or COBOL either by Required+Snark · · Score: 2
    It's not reasonable to say nothing will change in the next five years, but get real. Yes, a lot of organization will blindly follow the herd, but not everyone will. A lot of stuff will stay exactly the same.

    "The cloud" is not a magic carpet, and there are a lot of organizations who will get burned by falling for all the hype. I personally know a cloud based service provider that actually believed the marketing crap on reliability. When their cloud provider (one of the big two) crashed they had no backup and no recovery plan either. They were flat on their back for a week, and were still picking up the pieces a month after that. One more of those and they might just shut their doors.

    So here is another fad, and the inevitable backlash will come when it fails to deliver. So how dumb do you have to be to announce the start of a brand new shiny paradigm shift that will make everything really different in a blink of an eye. Grow up.

    --
    Why is Snark Required?
    1. Re:And there will be no mainframes or COBOL either by Psychotria · · Score: 2

      So here is another fad, and the inevitable backlash will come when it fails to deliver. So how dumb do you have to be to announce the start of a brand new shiny paradigm shift that will make everything really different in a blink of an eye. Grow up.

      There is no paradigm shift. "The Cloud" is just another way of saying distributed computing which was available in the 1960s and became popular in the 70s. It then started a slow decline because it was shit. Mostly it was shit because of network speed, but on the other hand it was shit because you relied on a remote location. It's still shit and I really hope this "Cloud" evaporates sooner rather than later.

  7. IT as a utility - we're already there. by zerofoo · · Score: 5, Insightful

    At our school, here's the list of stuff we pushed into the cloud in the last few years:

    Student information system (attendance, grades, IEPs, lesson plans - the lot). This eliminated an RDP server farm and a couple of SQL servers.

    Email - this eliminated a couple of Exchange Servers.

    Student data storage and applications - Google Apps eliminated most of our Windows and Mac student workstations. Chromebooks are cheap and easy.

    Firewalls/VPN - management of these devices is now in the cloud - goodbye to local firmware updates and far more flexible provisioning of devices.

    MDM - no longer in-house.

    In each case we realized cost savings simply due to sharing someone else's infrastructure instead of home-brewing our own. Security concerns in the cloud are overblown by those trying to save their jobs. The fact is that most small to medium size businesses can not afford to have the security talent that most cloud companies have.

    We don't make our own water or power - why should we try to build all of our IT?

    1. Re:IT as a utility - we're already there. by magamiako1 · · Score: 4, Insightful

      And then your Internet connection goes out.

  8. It's over.... by beheaderaswp · · Score: 4, Interesting

    I can see the writing on the wall, from the perspective of having my first IT job in 1983... It's over.

    No one should really seek to enter a non development position in IT. Because it is being snuffed out by "big computing cloud services" and the "appliancezation" of IT infrastructure. There will always be some high end jobs around. But the numbers (and the pay) are shrinking- fast.

    So pack it up kiddies. Almost 30 years of booming industry will be evaporating in 5 to 7 years.

    It is truly time to find something else to do.

    --
    Another consultant who stuck it out.

    "We are the Priests, of the Temples of Syrinx..."
    1. Re:It's over.... by Drethon · · Score: 2

      The same way code generation was/is going to eliminate software development? Even with code generation tools, we still need people with design mentality as that is where most of the work is, not in the implementation.

    2. Re:It's over.... by cfalcon · · Score: 2

      The push to centralize is usually driven by analysts who expect cost savings. But there's two other things that follow. The first is, if it becomes, even for a little bit, "expected" to run to a cloud, then you'll see a bunch of clouds forming to run to, each with some angle on why you should use THEM... and those clouds will themselves want IT ppl. The second is, there's downsides to centralization, and those downsides will always be there. Centralized places are a security risk because you can stack data in a place quicker than you can stack security, they are a connection risk because they rely on a lot of physical connections that your business would not natively care about ("Protesters across the country from you..." goes from "discuss with friends" to "now is your problem"), and they are a financial risk because they will gate access to your applications and switching from one cloud to another cloud will become as hard as required (serving the interests of the cloud providers, not yours), and they are a future risk because once something becomes a central repository in whatever way, it invites the government to start having meetings. Should these guys be allowed to do this based on their ability to market and provide services.... or does there maybe oughtta be a law?

      I just don't see the total gloom and doom.

  9. End of line by RubberDogBone · · Score: 5, Interesting

    Got laid off yesterday from an IT job I'd had for almost 15 years. Small company so I did a lot of things, from hardware to software to physical security, to sweeping the floors to to taking boxes of mail to the post office at midnight. If it needed to be done, I was the guy to get,

    So now this middle-aged man is suddenly out of work and looking at an IT field that is already vastly different than it was even five years ago much less fifteen. I don't have a clue what I am going to do. What I know how to do is of rapidly decreasing value and/or there are kids who will do it cheaper.

    I have no idea what I am going to do. Savings and severance will carry for a while but I've got to make a pivot to do something entirely different which pays well. My job may be gone but naturally the bills aren't.

    --
    Sig for hire.
    1. Re:End of line by pstorry · · Score: 5, Informative

      Having been in the job market myself recently, here's a few pointers...

      Skills are good, accomplishments are better. The skills are usually just there to get you past the filter - once your resume is being read (not skimmed) by a human, the accomplishments are what will matter.

      In the current market, integration and automation are the kings. If you think it can be done in the cloud, then assume it is being done in the cloud - and forget doing that as a job. The very best case will be that you integrate with it.

      If you work in Windows environments, you need to brush up on PowerShell. If you work in *NIX, then you'd think bash/python/perl should be your focus - but I'd suggest you get familiar with puppet/chef etc., because I didn't see a single job that required *NIX skills that didn't also require or express an interest in using a puppet-like system to automate configurations.

      There are some migration jobs out there - migrating users to O365 etc. Those jobs will pay bills for the next couple of years, but will dry up for obvious reasons. Feel free to take one in the short term, but keep looking for something else in the background if you do.

      Otherwise, throw your skills into some search engines and see what happens.

      Oh, and good luck. I hope you find a decent job...

    2. Re:End of line by Anonymous Coward · · Score: 2, Insightful

      Wish I had points to mod this up. I sincerely wish you the best. You might be able to bridge the gaps by finding a consulting gig.

      This is exactly what I'm trying to avoid. I've been in IT for nearly 20 years now... when I started out in the late 90s, it actually felt possible to "know everything" and flying by the seat of your pants was just how things got done. I don't even think I'd heard the term "best practice" until 2002. If you were good at what you did, you could run on instinct. It was, I daresay, fun back then. Now everything is so regimented and governed...

      Over the years I've moved around a bit, and done everything from helpdesk to system admin to IT manager to consultant and again to sysadmin. I got very comfortable in my role as IT manager (at a construction company that didn't really understand the role or value of IT), since I was pretty much a one-man-show for almost 8 years... but when they allowed me to hire a junior admin to handle some of the day-to-day stuff, all they saw was a young kid enthusiastically doing the grunt work for less than half what they used to pay me to do it. Never mind all the complex project work I was doing, never mind the vendor and client relationships I'd built, forget that I'd essentially built the entire infrastructure from the ground up... I was suddenly "redundant" and got RIF'ed. Out on my ass and replaced by a kid who wasn't even old enough to drink. Hopefully he's been able to do well. He was a good kid and I bear him no grudges. Sucked for me though.

      From there I went into consulting, thinking it would be a good place to pick up some of the skills that were growing in importance, and get my hands on some of the tech that passed me by because the company I'd been at for the last 8 years preferred the "bubblegum and paperclips" methodology to spending money on IT. I was hired into a senior role due to my years in the field, and did manage to learn a few new tricks, but I felt like a dinosaur next to these twenty-somethings who were genuinely excited about tech and were already schooled on stuff that I needed to try and catch up on. My many years of experience was less applicable than their months' worth.

      Part of it is a passion problem... I'm 40, and have all the requisite grown-up worries that come with marriage, home ownership, kids, divorce, remarriage, home ownership take 2, etc., etc., etc... when I'm lucky enough to have a little spare time for myself, I sure as hell am not going to use it to read about anything IT-related or build labs in my basement. Information Technology is what I do, not what I am. However, many younger guys and gals who are starry-eyed and excited about their futures have genuine passion for filling their minds with tech, and are not burdened by years or decades of "deprecated" knowledge that seems to get in the way of learning new things. They're also not burned out by years of being the scapegoat when things break and being invisible when things work. And they're cheaper.

      Tribal knowledge has some value in IT, but not as much as in other fields. Eventually that mainframe is going to die, be replaced with some shitty Wintel solution, and knowing your way around an AS/400 isn't really worth anything anymore. Age is a liability, and experience is like being a musician... you might be a maestro, but if you're playing an older style of music as opposed to keeping up with trends, your audience is going to dwindle until you can't find gigs anymore.

      I'm hoping to have an epiphany one day soon and figure out what I want to do next... because I don't want to do this any longer than I have to.

  10. IT != SA by CountZer0 · · Score: 2

    Information Technology covers an incredibly wide range of careers, only a small portion of which are system/network administration related. Yes, in some organizations, the "cloud" may reduce the need for traditional SAs, but it is simply the latest in a long-term trend of reduction in force for that sector.

    Automation has already decimated the SA workforce. Long gone are the days when companies needed armies of SAs to maintain datacenters of servers. The datacenters are still there, but are being maintained by much smaller teams of SAs using automation rather than manpower. Many large corporations who haven't (and won't) embrace the cloud, have already gotten rid of their SA staff, relying instead on vendors like HP to provide both hardware and SA level support as a bundled package. There are still SAs, of course, but they increasingly work for one of the main vendors, rather than being distributed throughout many corporations.

  11. Re:Disturbing by Anon-Admin · · Score: 5, Informative

    It's not that we are denying it. It's that we have seen it before.

    Windows NT was going to eliminate the need for corporate IT. It is so simple that the secretary can manage the system. (Yes, Microsoft sales used that as a selling point)

    Central server management was going to eliminate corporate IT. It would be so simple you just have to hire a person to push a button and the problem is fixed.

    Self Healing systems are going to eliminate the need for Corporate IT. The systems will detect an issue and heal without the need for IT personnel.

    Outsourcing to India will eliminate the need for Corporate IT. You outsource all your systems and management to a data center and share the cost of the infrastructure while getting the best of the best to work on it.

    Now, Clouds are going to eliminate the need for Corporate IT.

    History shows that each has been wrong. Dont misunderstand, each did some small part of what they claimed but over time it all becomes more expensive and less productive.

    Clouds are no different!

  12. So who does it in the "cloud" by guruevi · · Score: 2

    Someone has to assemble these computers and repair them, replace the hard drives etc.

    With cloud you're paying overhead and profits on all of the things your IT guy has to do anyway. Your virtual host still needs hard drives and expansions and software updates. Swapping a hard drive once in a while is not a big deal.

    Cloud is great if you only need very small quantities of something, perhaps for testing or a resource you only use once in a while. If your core business is dependent on it, unless you have a small company that can't afford a full time IT guy, you pretty much can host, colocate or rent your own stuff cheaper than an entire cloud stack.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
  13. Timesharing by naris · · Score: 2

    Back in the day (60s,70s,80s) "The Cloud" was called "Timesharing" on Mainframes. "The cloud" does not eliminate infrastructure, it just moves it to another company that you pay fees to. There will always be IT pros "pulling all-nighters, swapping in hard drives or upgrading systems", but they will be working for the cloud hosting companies (and probably be offshore). Also, chances are that companies with stable infrastructure needs that don't expand and contract all that much (which is most companies) would of saved money overall if they owned their own equipment instead of renting capacity from a cloud company. After all, the cloud company has to pay for all the same things *and* make a profit (often a very substantial profit), which will be reflected in their fees.

  14. Cloud Shmoud by sycodon · · Score: 5, Insightful

    "The Cloud" is a buzzword created to fool executives into paying for Other People's servers. Executives see it as some magical technology that is fool proof and infallible.

    The term should be eradicated, preferably with fire.

    --
    When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.