Slashdot Mirror
Moving Away From the IT Field?
irving47 writes 'With the economy the way it is, it's a little iffy to even think about switching careers completely, but lately, I've gotten more and more fed up with trying to keep up with the technical demands of companies and customers that are financially and even verbally unappreciative. While I might be good at it, and the money is adequate, I'm curious to hear from Slashdotters who have gone cold-turkey from their IT/Networking careers to something once foreign to them. How did you deal with the income difference, if any? Do you find yourself dealing with people more, and if so, how did that work out?'
you might want to think about nursing. My ex-wife was an RN and she made really good money right out of college.
You have to clean up poop sometimes, but it's decent money.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
I'm an ex-Navy guy. My military career field was journalism and public affairs. When I got out of the service I went directly into IT.
The same factors that governed my career change would likely work in this, and any other similar situation:
1. Identify things that you LIKE to do.
2. Of the things that you LIKE to do, do you also possess marketable skills doing them?
3. Can you put those skills on a resume?
4. What can you do NOW to add credibility to your new career?
Work those things out and making the leap should be fine. Beware, leaving IT can often mean leaving a good paycheck. You'll want to get your finances and lifestyle in check before making the jump.
Brought to you by Frobozz Magic Penguin Fodder.
I used to work on the docks in NJ as a longshoreman during the summer and winter breaks from school in the early to mid 1990s. If I had stayed down there I would have close to 20 years in already, be getting paid close to the same amount I get now considering the hours that I put in plus the extended periods of no work each and every time the economy takes a down turn. I would have 6 weeks paid vacation every year, great medical, stable work, and no politics or being treated like an overpaid janitor. Unions are very good things people and sooner or later this country is going to figure out. The books are now closed and probably won't be open again for 5 years so even though I still have a union card, I can't get a job down there till federal government determines that it needs more workers thanks to the NYSA, not the union. I am trying to get a job as a US Customs Agent now. Sure I ain't going to be making a lot of money, but the benefits, 40 hour work week, and stable steady work means that it actually comes out to about the same as I make now.
Seriously. You can start with one bag of seed and a few plastic buckets and sell to local businesses (especially organic businesses and asian stores since they sell larger quantities) and scale up from there. Inventory isn't a huge problem since it only takes 72 hours to grow the sprouts, and you can buy the seed by the 25kg bag.
Obviously, I'm simplifying things, but honestly it's a business that's incredibly easy to get into, resistant to non-local competition due to the perishability of the sprouts, and if you can 'get it right', you can definitely market on quality
"Einstein argued that [...] God is not capricious or arbitrary. No such faith comforts the software engineer." ~ Brooks
Actually man, I make more money selling magazine subscriptions, than I ever did at Intertrode!
Only bad thing is I have to pretend I'm a recovering crackhead.
-Steve
I was working as a DBA in the mining/exploration industry until a few years ago. I got sick of constant corporate takeovers and mergers that went with the industry at the time, it's not fun looking for a new job every 14 months because some other company bought out the exploration rights and had their own staff and systems. On top of that, after my last redundancy I travelled around Europe and swore to never again look at a drillhole data log. Now I work as a civil servant overseeing the Thoroughbred, Standardbred and Greyhound racing industry. It's taken me 5 years worth of work here to finally get back to the level of income that I had at age 23, but the job satisfaction now is immense. It did take a few years to adjust and slowly work my way up the food chain but I wouldn't go back to IT and ungrateful/idiotic/anti-technology positions again. Ultimately I found that job satisfaction and regular hours far outweighed the extra money I made in IT.
Spelling and morals are both still optional?
IT jobs get absolutely no respect any more.
They get paid crap.
They have *ON CALL* work.
They have to read the minds of dolts who make more money (and work in a more sex balanced environment and who often get to go out drinking on the company dime).
I had to beg our manager to take the guys to lunch. And he wouldn't spring 15 bucks for an appetizer.
Meanwhile the other side of the building is meeting for drinks at the bar at night dropping easily 10 to 20 bucks per person.
At my friend's company, the IT folks get up at 6am, get left at work while everyone goes out drinking for extended lunches (because they are "sales and executives")-- entire company is smaller than my last team. Executives my ass.
Somehow, we let them do this to us. When I was getting into the field, we were priest kings in air-conditioned rooms with complete power. But with each passing year, we underbid each other and passed control over to people who worked us to death.
Leave the field.
If your in it, learn to fail gracefully.
Negotiate for more money and leave when they don't give it to you. Leave them in a lurch.
This all sounds like a troll but it's more bitterness seeing complete idiots making 6 and 7 figure salaries while the "intelligent" folks are working as slaves.
How did it come to this?
She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
I'm completely jaded with the IT industry after having spent the past 10 years installing toner cartridges and mapping network drives for people that show very little gratitude. I tried my best to move up the corporate ladder, so to speak. I started out at the bottom and slowly worked my way up passed junior admin, helpdesk, and into senior technical support. Then I hit a vertical limit at one company, with no choice for further career progression. I looked around and evaluated my skills, but everything pointed to a horizontal move. With my desire to have a stable, decent paying job, I had inadvertently boxed myself into a position which was going to be almost impossible to get out of. My skills were clearly tailored around supporting users, with some network admin and even lecturing experience. Then, a miracle happened, I got laid off from that job and that's when life started. Suddenly a thousand possibilities entered my head. And that's where I'm at right now. I'm taking 6 months off, I put my condo up for rent and I'm going traveling to Africa! I'm hoping to accomplish quite a few things when I get there, re-focus my efforts and rejuvenate my enthusiasm, when I get back I want to start my own company, I'm tired of working for people. I want to experience owning a company firsthand and seeing my efforts pay off, literally. I'm tired of making shareholders richer and richer with each passing month. So if you skipped all of that here's the sum up. If you don't enjoy what you do, take some time off to figure out what it is that you want to do with yourself. Emphasis on 'time off'. They say that people change careers 5 times in their lives. This change, for me, will be change number 1 and I'm looking forward to it like you cannot believe.
-Zero Tolerance for Zero Intelligence-
I got out of IT after more than 10 years in the field (and CTO-ing for a public company in my last job) as I finally got fed up with it. After a longish sabbatical, I started a small bakery/coffee shop. I'd say it is as big a change as you can axe for, and I have been pretty happy so far. I still use some of my mad skillz, but since I went the hard way - designed and built my shop and equipment more or less from scratch - I had to learn (and I am still learning) a lot of stuff - from carpentry, construction work and machinery to advanced chemistry. ;)
At the beginning, the money wasn't that good and it was hard work and long hours, but eventually things picked up and now I am better off than I used to be. The biggest benefit outside of the pay is the free time -- now I have a lot of time for side projects. Half are somewhat related to extending the business, the other half are just things I like. I don't push it very hard though, because that was what I was running away from in the first place. Overall, I regret it I didn't run away from the field earlier. That said, I got into IT by accident, and I didn't like it that much.
Good luck.
I'll take your job!
I hit the same point about 2002. The Dot Com thing had soured and I was just tired of the whole game. I did a two year volunteering gig in the South Pacific... and never left.
It's fascinating, because a lot of the stuff I was doing when I first arrived here was the same I'd been doing 10 years before (I mean literally the same technology). Since then I've moved along and now I'm pretty much current with the kind of things I'd likely be doing back in Canada (technical manager for a local university institution). Just this week I submitted patches to a wireless network driver for the latest version of Ubuntu. So what's changed for me? Just this:
IT work in development has taken me to cities, towns and villages in Fiji, the Solomon Islands, East Timor and Vanuatu (where I now live). I'll be off to South Africa in a little over a month.
I have faced crazy demands in the past (Windows activation from a place with no networks and no telephones? Keeping the minutes for a week-long meeting in a town with no power?) I've had malaria and been hospitalised with kidney stones from dehydration. I've shared the room with rats, roaches, fire ants and geckoes. I've slept on cement and eaten more cold rice than I ever thought possible.
But I've also had breakfast in the clouds, been to the brink of volcanoes, rambled in rain forest and snorkeled in coral reefs so often that it's run-of-the-mill, dined with Ministers of state... and helped make people's lives a little more liveable.
The work is engaging, challenging and stretches one's creativity to the limit, trying to figure out how to mesh Internet technologies with cultures largely unchanged in the last 3000 years. It pays a tiny fraction of what I used to make, but the rewards are infinitely greater.
Crumb's Corollary: Never bring a knife to a bun fight.
- Skills [read buzzwords] change every few years - Check
- Buzzword compliance resume is more valuable than actual skills - Check
- Your job can be shipped off to India, China or the Next-Offshore-Location any single day - Check
- You make a lot less than what people think you do - and a lot of your staff hates you [esp for Administrators] - Check
Did I miss anything ? So what's there NOT to hate an IT Job ?
IT isn't about training, it's about being able to find answers and solve problems of a technical nature. Development requires training, although the best developers I know are almost entirely self-taught. The best in IT usually come from other backgrounds, and have an aptitude for technology. The "pure techies" don't go very far. Throw in an MBA, CGA or PMO certificate and you are moving up in IT.
"You are not a beautiful and unique snowflake."...Tyler Durden
I just started lighting Altadis Behike cigars with $1,000 bills. As long as I smoked at least a couple a week, my income stayed about the same.
I've calculated my velocity with such exquisite precision that I have no idea where I am.
Sure, people selling little baggies of things will prosper and grow. But it ain't going to be cheerios.
Honestly, I'm an Indian IT guy who looks like this and is a straight edge vegetarian. But despite all that, twice in Portland, people have stopped me and asked me for some weed.
Now, there's a market which expands during a recession.
Quidquid latine dictum sit, altum videtur
I spent about 15 years in IT (programmer, sysadmin, webmaster, web dev, consultant). 5.5 years ago consulting was slow (if you knew my town, you'd know why) so I was looking for a full-time sysadmin gig. Just so happens the biggest local UNIX shops are observatories - the kind with telescopes.
I was applying for sysadmin jobs when a part-time gig operating a small telescope came along. I didn't know a whole lot of astronomy (okay, I knew woefully little, and had never had a single class in it) but the telescope was controlled by UNIX and Linux boxes, and I sure as heck knew those. I had to learn about "right ascension" and "declination." I picked up some other part-time jobs, so my worst year (2005?) ended up only being 80% less than my best dot-com year (2002).
About a year later, I started doing sporadic laser-safety stuff at a couple other observatories. Not in terms of actually working on the lasers, but in terms of making sure they didn't, um, hit any airplanes. :)
A couple years in, some folks who were using the telescope a lot decided that since I was a techie, curious, and actually talked to them (they used an AIM chatroom for communication between collaborators on a couple continents, and all my fellow operators were thoroughly non-instant-messaging sorts), they'd train me to use their data-taking setup (xterms and some custom GUI apps, running in VNCs over an SSH tunnel). So before long I had entries in ADSABS and a .gov email address and life was getting weird.
Last year, after 4 years of being a computer geek surrounded by astronomers, I signed up for an online graduate certificate program in astronomy, in hopes of learning what all those strange words meant. This spring, being in a graduate program weighed in my favor and I got a full-time job as an operator-in-training at a (much larger) telescope, which basically pays enough to live on, here (and has a lot of upside potential).
So... pros and cons of going from IT operations to technical work in science operations...
Cons: ;)
You'll never hear anyone talking about crazy dot-edu or dot-org pay.
The survival of your job depends in part on survival of their funding.
If you're a lone wolf or primadonna, operations is not the place for you.
Work ethic may be different; no foosball table.
Pros:
Science abhors a vacuum between people's ears, so everyone you work with will be smart in some way or another.
Scientists actually recognize and appreciate the fact that You Make Things Work. (egad!)
Hiring authorities often equally happy with a degree in their science, some other science, technology, or engineering.
Stress level can be significantly lower in some cases (like mine).
Oh, and FWIW, science-y places also need electronics engineers, electrical engineers, mechanical engineers, programmers, sysadmins, builders of instrumentation - all kinds of techies.
Just sayin'.
Village idiot in some extremely smart villages.
I hear people complaining about their shitty IT conditions, and I really do sympathise.
I used to be in a similar situation, before I learned a bit more about Economics and applied it to job hunting.
Supply and Demand alone suggest jobs in places like the Games industry (to which most male gamers under the age of about 25 aspire) will be horrible. The massive supply of labour will be chewed up and spat out by the fickle industry, paid low money and treated like crap.
Likewise, many people in IT are on the cost side of the ledger, where a company is always going to be seeking for reductions in cost and increases in efficiency.
My suggestion? Find an industry which is old (and thus has well established work principles), deeply unsexy, and (if you can) look for jobs on the income side of the ledger. And then be the guy that steps up to take responsibility for safe-guarding that income, the guy that can step up and speak truth to power and be taken seriously because it's your job to make sure that $100m, or $1b, or $10b revenue stream never ever ever stops.
In my case, I discovered the logistics industry and found a programming job at the largest company in my country maintaining the codebase responsible for 80% of their sales (and climbing).
Good money, normal 9-5 hours, prohibited from doing overtime, a proper infra team to manage the hardware, a proper ops team to deploy and run our software, and a reasonable ability to requisition just about anything we need, because The Spice Must Flow.
I would imagine that similar jobs to mine exist in all kinds of places that sound really boring, places like power companies and garbage recycling and anywhere else that needs a lot of IT but will never be mentioned on the front page of slashdot.
My IT Training came from on-the-job. The Navy was still all dumb terminals and MSDOS. My job, as a journalist, eventually required the command provide me with a system for desktop publishing. That meant either Windows 3.1 or MacOS 7. Fearing Mac, they gave me Windows and Aldus PageMaker. When the command began rolling out Windows to the rest of our personnel, I was the only person on-hand who had any knowledge. I became Tech Support. When they began networking the machines together in a workgroup, I assisted with that as well. Not to mention that cabling a ship for closed circuit television is only a few steps removed from cabling 10Base2 ThinNet.
When my ship pulled into Hawaii, I spent my liberty installing Slackware on my personal laptop. By the time I got out of the Navy, I had plenty of experience with Windows, Unix (Linux), and networking. I got a low-level, low-paying job at a financial corporation and quickly worked my way up by proving my ability and obtaining requisite certs, etc.
Brought to you by Frobozz Magic Penguin Fodder.
I think there are a lot of things being mixed up here. My job in IT sucked. So I left and am now a freelancer doing web related stuff, and working as a teacher, also on IT related subjects. My point: it's having a boss that sucks, not the actual IT. When I come in from the outside and I'm being paid big bucks for it, I get respect that I wouldn't if I were a wage slave. The reason they treat salespeople better is that they know how to market themselves, whereas there is this persistent image of IT people as Rainman types who you can kick around. Unions would help, but just leaving works too. In France we call this "voting with your feet".
You hit upon something here. There are a lot of IT related fields. One can be a sysadmin, a DBA, an admin watching over developer projects, an architect who designs infrastructure, the network admin who sets up the core/edge structure, the implementers who implement, the security auditor, the corporate compliance people, etc.
I wonder if people might be better off changing their IT field, rather than leaving the industry completely and starting from ground zero. For example, changing from a sysadmin specialty to a DBA would require a lot less retooling than changing completely out of IT and not having any common skills.
True - and since I have been brought up on a farm I know that weather is an important problem to worry about.
If you really want to see the scope of troubles in different jobs I suggest that you can watch Mike Rowe in the show "Dirty Jobs".
In reality - either you have a job filled with problems or you have a dull job where you are never challenged intellectually and you become stagnant.
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
It's hard work. I spent two weeks working on a sheep farm. 12 hour days, very physical work. Not to mention living in a state of constant sexual exhaustion.
Sexual exhaustion? . . . . Were you pitching or catching?
Not quite the same, but...
I work for part of a University that has a name that sounds like a telemarketing firm.
Frequently, one of my high level clients will call me in a panic and leave a message. I call back, but 50% of the time I get screened by a receptionist who just assumes I am trying to sell something.
If the client is a jerk, I don't even bother to explain. I'll wait until they call back and then tell them I got screened.
This happened to one client 5 or 6 times. Finally I explained to the secretary who I was, so the call would go through. The secretary said, "Oh, I know who you are...but she gave me a list of words to use to screen calls with. And your unit has two of those words in the name. Besides, it's fun to watch her get mad when she doesn't get the call."
I don't blame the secretary at all. But then again, you could only get away with that in the public sector.
No reason to lie.