Slashdot Mirror
IT Jobs To Drop In 2009
ruphus13 writes "A new Goldman Sachs IT report recently released states that IT jobs will be dramatically reduced in 2009, starting with contract and offshore developers. From the article: 'Sharp reductions likely in contract staff, professional services and hardware, and almost no investment in cloud computing.' The article goes on to say 'The CIOs indicated that server virtualization and server consolidation are their No. 1 and No. 2 priorities. Following these two are cost-cutting, application integration, and data center consolidation. At the bottom of the list of IT priorities are grid computing, open-source software, content management and cloud computing (called on-demand/utility computing in the survey) — less than 2% of the respondents said cloud computing was a priority.' Postulating a 'pointy haired boss' problem, an analyst goes on to say, '[Grid computing, Open Source and Cloud computing] require a technical understanding to get to their importance. I don't think C-level executives and managers have that understanding.' But they do control the paychecks ..."
I'm sorry, but it's hard to take your message seriously when your company name is Pund-IT. From the name, I think you'd have been better off with Pun-dit. Or Pwnd-IT, which is pretty much what a lot of consultants are going to be feeling like next year.
At any rate, anyone who has been around business through a down-cycle or two would know that this is common sense. New programs, new ways of doing things, are saved for when the budget Gods are feeling generous with surpluses, not when eveyone is tightening their belts. There are, of course, exceptions to this... but anyone who thought that, in general, discretionary spending would increase over the next year really needs to have their head examined.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
Well having to have had to manage a team in the Phillipines, miscommunications, missed deadlines, inability to follow instructions, redundant programming, lack of teamwork or cooperation, poor scheduling and more makes the low pay only part of the cost when the overall expense of the project eventually becomes 5-10 times what it needed to be had we hired local developers.
Outsourcing only pays off for VERY well managed and VERY well organized 3rd party organizations that you can trust 100% and as a rule, they don't exist because they don't exist ANYWHERE. You need to have an onsite presence much like IBM and Microsoft has in order for offshoring to really payoff. Otherwise you are not saving anything and may even be paying more... regardless of what some pitchman may tell you.
This is my sig. There are many like it but this one is mine.
One of the age old problems is the assumption that IT for most companies is simply capital expenditure. ROI is hard to measure for IT for most companies.
Picture a DR situation where an office is lost to fire. If the company didn't invest in adequate protection then that company is now often out of business losing entire client databases or even contracts. Now proper DR would not only save all your data so you can keep doing business but potentially you might not even have downtime as is the case with banks. This is of course federally mandated but the company I work for is a private entity and practices the same philosophy.
Then of course comes the automation, once a task is automated it is no longer reflected in ROI even though the system is still in place years later supporting it.
Course I'm one guy managing over 40 servers across five sites so I don't foresee a reduction in IT staffing anytime soon for this company.
You're right though, tight times means you spend the extra time to finish your deployments instead of investing in new projects. This means your environment becomes more cohesive and the new stuff later will snap in easier since everything will be well documented by then.
Consider the downtime a nice roadblock allowing you to audit everything you currently have to make sure you are using everything efficiently.
Virtualization for the win, we'll utilize our hardware more effectively while increasing functionality.
Seriously....I look in the paper and it's filled with ads for drivers. That and health care professionals. And as I would rather stick a pencil in my eye than work in health care, I figure my misanthropic ways would be better shifted toward driving.
I'm 46 and have to basically totally switch careers as there are just aren't any jobs in my profession anymore. It's over saturated. I hardly ever see an ad for IT or anything related in my area. As scary as it sounds, changing directions even this far into life may not be a bad idea.
Even with fuel prices sky-high, trucking will be with us for a while as lets face it....everything within your eyesight right now reading these words was all delivered or transported some way via a truck (unless you're looking out your window at a tree or something).
"Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
You've been lucky. After the "*does it*", the usual response from the ones who want it done is "But I wanted this, this, and that". Where "this, this, and that" are requirements which were never brought up before and which are completely beyond the capabilities of the products you were integrating.
that offshore jobs will go first. They're cheaper than local jobs.
Only in the short term. What's happening now (based on my anecdotal evidence, which is all one really needs here on /.) is that a lot of large companies are realizing this. Difficulty in communications, poor timing (What, you need that fix now? Sorry, you'll have to wait until tomorrow morning), and some of the shoddiest work you've ever seen are all contributing factors.
On the surface ,it's a very appealing model: you write up some requirements, communciate them to your offshore team and wow! magic! they return to you a finished product.
But here's what they don't tell you in the brochures (again, based on my experience managing and working with offshore vendors): a) if you don't spell out every single technical detail - almost literally to the point of writing the software yourself -- , you can't rely on them to do it right. b) you can't rely on them to communicate to you the things that they need clarification on, unless you are ready to spend a lot of time asking for t. c) the code you get back wll be virtually unmaintainable, with no thought given to refactoring, common functionality, or future mainitenance d) most of the development seems to be done by people with low experience (just out of the schools, which don't seem to teach anything relevant to the real world) and little skill e) if they have issues, do not expect to learn about them unless you constant ask for them. DO expect them to sit idle and not take any initiative if an issue occurs.
So all of this goes to say: it looks too good to be true, because it is. The old saying is that you get what you pay for -- and it still holds true. And after many years of budget overruns and software that doesn't do what it's supposed to do, companies are finally beginning to realize that.