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 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.
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 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.
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 was laid off from my IT position.. I live in Ohio.. everyone is laid off. All I know is computers. In a past life I was a paramedic but figured I didn't have the compassion needed for that job. I understand computers and love to do it. Thats why I chose IT. About 6 months ago I took a leap and opened my own computer repair shop. Only cost me about 2k to get the doors open. No stock of parts except the boxes of crap I had around my house. I am now making profit after 6 months. I love it. I have no one to answer to but myself. The customers are very thankful that there is some place they can go that will actually fix there issues. I even have some older retired guys who just come in to hang out. I have no experience what so ever in running a business. Learning curve is not all that hard. Luckily my neighbor is an accountant and helped me in that area. The first 2 months were kind of scary not having anything to do. Played a lot of pocket tanks with my friends. Now I have an office that I don't even go into because I have so much to do. If your an honest person that truly knows how to fix computers. I am sure you would be a welcome asset to your community. Oh yeah and the 2 mile drive to work is SWEET!
MISSING - Sig file. 2 years old black and white and very funny. If found please email me.
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".