Slashdot Mirror
Which IT Careers Are Hot and Which are Not?
necromante asks: "I've been working on different IT positions through my career: support; some networking; DBA; web development; project management; even working on the client side for a little while. However, I don't feel like I am really a specialist on any of those subjects and I feel I need to focus on a particular field. So, I decided to ask for some feedback before making my decision. I understand that this depends everyones tastes, likes and dislikes. However, I would like to have a better idea of which are the available options, and I hope the results of this discussion can benefit other readers. Is there any IT career that I should consider more than the others? Which are the emerging fields? Is there any industry I should focus on in particular? Which careers on IT are actually more in demand and which ones not? Is it a better path to focus on moving into management?"
I've worked for a number of people and myself one thing that seems to come up is that good techies don't always make good managers. So don't assume that managment is right for you (or that you would even enjoy it).
Cheap UK and US VPS
A lot of demand has to do with your demand knowledge. I don't know if you could say with a broad stroke that devs are in more demand than DBAs or whatever. If you have financial experience for instance, demand is pretty strong across the board. You need to consider the industry you want to work in as much as the role you want to play.
Which careers on IT are actually more in demand and which ones not?
Editor who doesn't rely on spell check.
Your sig(k) has been stolen. There is a puff of smoke!
When you were young, did you ever play video games with an older sibling where they played and you watched? Your brother would insist that you were "a team" and wouldn't let you play. Being a manager is like being the little brother, but you do get to fire the other guy if he dies five times in a row on level 8-2.
Seriously, if you like something, why stop doing it and start just watching people do it?
Oh, money.
Use the Firehose to mod down Second Life stories!
Personally, I value breadth over depth. And I'm going to propose a reason why everyone should also: in the world of computer science, at any minute a once vital skill could be obsolete. Granted, it doesn't happen often (as we still need workers to maintain cobol & fortran code) but, instead of spending my free time hunched over Enterprise Java Bean projects learning their delicate intricacies, I find myself learning about Ruby, Spring, Hibernate, etc. Now, I might not be an expert in any of these fields but I may be glad when their time comes. All good things come to an end--and if EJBs were to be retired, I'd certainly like to know my way around these other frameworks & tools. I think the same can be said about fields of computer science. Be wary of the web developer that doesn't know the first thing about networks & server/client communication--that's often a pitfall for security.
So if you want my honest opinion about which "are hot or not," I think they're all pretty damn hot and I bleieve you can find money in any job where you make yourself usefull & valuable to a decent business. I find them all attractive because I enjoy setting up networks in my house and playing network administrater even though I don't do it at my job. I love networking Linux, Windows, FreeBSD, Solaris, etc. and I like toying around with different databases. I love to start new projects that rarely go anywhere but leave me with more understanding of how technologies or products work. I'm not a "trained expert" at any of them though, most importantly, I feel that I could easily become one if a situation deemed it necessary. If you don't enjoy doing some of these things--DON'T DO THEM. Who cares if they pay alot or are "hot"? I'd rather die happy & poor than rich & sad. Of course there is, it's the career you enjoy the most
Choose your path wisely.
My work here is dung.
I think it all depends on the person and what they like. I'm currently an IT Project Manager while dealing with managers and I can't stand it. My goal is to get another Sr. Systems Engineer/Manager position that entails working with various Operating System environments (Solaris, RH, Windows, etc.) while doing IT projects (rollouts, migrations, etc.).
Again, you need to decide on what you feel is right. Obviously, money always come into play here, but it seems like you already have a wealth of information and a broad spectrum of experience that you have the capability of going into any IT arena.
Good luck.
I hear it's lovely over at tech support. You get to talk to n00bs all day and make them run around in circles because it's the "fixing ritual" and stuff.
No seriously. BOFH is the field you're after.
"Women are just like ninjas; They lie even when it is more convenient to tell the truth." ~ Unknown
Where I work, the opposite tends to happen. If you're not that good technically, you tend to bubble up to management. I'm not saying they're complete idiots, just that they're not the best technical people. I still don't think it's the best way to find good managers though ... they may suck at that as well.
What's hot in my area (washington metro)? security. And based on some of the crap being pushed on us, it takes very little experience or understanding of the system to force functionally useless requirements on us. (HSPD12, anyone?)
You then also have to look at not just region, but industry -- informatics is becoming more significant in some industries, but not in others.
Then there's issues with the size of the company -- specialization may be good for large companies with a massive IT workforce, but it's not desired in smaller companies with a small IT staff.
From the sounds of things, you need to look into systems analysis -- and review your organization, and your network of contacts. What's good advice for one person is most likely not what's good for anyone else.
Build it, and they will come^Hplain.
Almost all areas are 'hot', but that doesnt mean anything. The one that will STAY hot for you, is the one that you love enough to continue your education throughout your career, and dont just pick someting to do for a paycheck.
If you love a particular area, your constant learning and improvement will lead you into related areas and keep you relevant throughout your career, you can move into consulting, writing and development within your chosen area and never miss a beat.
Never chase a paycheck.
Any provided you live in India. Gotta love cheap phone support.
"Choose a job you like and you will never have to work a day of your life" - Confucius
That's one of the better quotes out there. I've been in the Unix Sysadmin/Programming areas
for 10 years now and while I haven't found it all easy going and wonderful, I DO like what
I do, which is a huge advantage to quality of life in a career.
Pick something from the areas you listed that you enjoyed and work at it. Don't be too
concerned about "what's hot". If you have the fundamentals (such as a CS degree or equivalent experience) you will be fine.
Best of luck.
Eagles may soar, but weasels don't get sucked into jet engines
One area that is rapidly growing is Cisco VOIP. I've been studying for my Cisco CCVP cert and it's more complicated than you might think. Most companies love the fact that they can use their existing network equipment (routers/switches) to replace all their PBXs/ACDs, not to mention free inter-network calling.
I work for a large company and we're currently in the process of a ~5 year migration from all legacy PBXs to Cisco Call Manager. Many other companies are doing the same. Just about all new offices are built with either Cisco or Avaya VOIP systems, but most companies go with Cisco since you don't have to be concerned with compatibility. (eg. A high-end Cisco router is also your telephony gateway where the T1s are converted to VOIP.) As you can guess, this calls for some highly specialized skill sets (eg. Call Manager/ICM/IVR + Cisco Networking/IOS, etc.) which not a lot of people have. If you're certified, you will NOT have a problem finding a job.
$7.95/mo, 200 GB disk, 2TBxfer, MySQL, PHP, RoR.
Seriously. Some of the worst jobs have great security and pay well. Look at COBOL programmers - it's probably better to say you're a piano player in a whorehouse than to admit you mind legacy COBOL installations, but I hear that they're pretty darned good jobs. The "coolest" jobs usually pay squat, have lousy hours, are highly competitive, and experience high burnout. (see: Elelctronic Arts).
On the other hand, you can always pursue what you really love, and hope that you happen to get lucky and that your obscure interest is the Next Big Thing (TM). That's how the really great ones did it. Of course, if you did a better job selecting your parents (see: Paris Hilton), the career thing wouldn't really be an issue and you wouldn't be in this boat. So based on your track record, going with the chance part isn't such a good idea for you.
Is it just my observation, or are there way too many stupid people in the world?
Today's "hot" career is tomorrow's outsourced to India dead-end job. Stop caring what's popular and focus on what you like doing the most. If you like doing all sorts of different things, then keep on doing that!
It doesn't mean much now, it's built for the future.
I think the question is somewhat loaded, but I suppose everyone has a perspective. In my opinion VOIP and Network Security are hot career paths. I have been working with both (Cisco) over the course of the last five years and the market is very good for specialized Network geeks. When looking for marketability on the job boards VOIP/NetSec are paying more than my other skills.
.02
The one thing I do know for a fact is if you are diversified in a couple of "hot skills" your marketability goes through the roof. If you throw management experience along with that you can make some pretty hefty sums AND find a job you like.
My
When the only tool you have is a hammer, every problem looks like a nail
I have to agree with this. I'm a business owner, with a partner. I'm the hardcore techie here, while my business partner has a background in video production and marketing. He tends to take on the true management role here while I worry about actually getting the work done. It works out well as I'm not a great manager but I can get the work done when it needs to be.
The thing I have noticed is that a lot of people in a more technical role feel that they would be better in charge but in reality would probably just hate the position. I love being in control (hence owning my own business) but at the same time I'd rather leave the more managerial duties up to my business partner while I really worry about the technical side of things.
I have been a manager at a few places and while I did a decent job and my staff liked working for me, but I didn't enjoy the role as much as I enjoy being in the forefront with my technical skills. I did learn a lot about running a business from these positions which is a benefit now, though, and don't regret having been a manager. I just didn't enjoy it.
rm -rf
It happens in a lot of places and it's called the "Dilbert Principle". Unfortunatelly, it is usally a self-sustaining process.
If you are having this much doubt about what you want to do, for Gods sake, get OUT of IT.
Go into the resturaunt business. run a mcDonalds. Get into the auto mechanic shop business. You can probably make better money herding 10 people cleaning houses. (That right there is a six figure a year job, for basicly managing a crew of people who descend on a house, clean, sweep, vacume and leave, repeat ad infinitum, scale as large as you want)
Of course, considering your lack of direction, you may not be the best person to run a business. Perhaps you should stick to help desk.
Oh yeah...I'm coming for all your asses.
12:50 - press return.
About ten years ago, I sold my soul to Microsoft and haven't regretted it yet. I work for a healthcare organization that's a Microsoft shop. I started as a database developer, switched to SQL Server administration, and have been a web developer ever since.
I personally prefer development over administration. Being a database administrator was a lot like being a firefighter. There were long periods of boredom where everything was running smoothly, coupled with late night crisis modes with huge pressure to get critical systems running again.
As a web developer, I get to do database work as well as creating web applications. I create a lot of things to make people's lives easier, some of whom are patients to our hospitals. It's interesting work and I get fairly generous praise heaped on me by coworkers and customers. The really crazy thing is that they pay me quite well to keep doing it.
I have the same problem. I am an IT Multi-tool. I am not the best tool for any particular job, but I may be the best and only tool you currently have for the job at hand.
...
I have the following credentials:
Degree in Computer Science - No I didn't learn everything I needed to know in college, but that paper opened a few doors.
10+ years experience with computers in a networked environment.
Experience using and troubleshooting computers ranging from DOS to Windows to Linux, with a sprinkle of Unix.
Programming in C,C++,Java, VB and VBA
Knowledge of HTML
Experience in maintaining production servers for critical tasks.
Experience with peer-to-peer networks, hundreds of nodes.
Experience with Databases,MSSQL and MySQL know basic to moderate level SQL.
Experiences with Apache and IIS.
Command line scripting from DOS Batch to Linux Bash.
Tons more things I have just "worked" with as needed.
I have always been a "jack of all trades" in terms of computer work. Recently I have been specializing, not by choice, but by necessity in Phone and Data Networks. I have taken several weeks of training in ACD and Phone PBX systems. I have been setting up our phone ACD for about 2 years now. About to start working closer with the PBX hardware as well. It is an interesting niche.
If you are just looking for the latest "hotness" in computers it is security. But that type of job could well leave you stressed out with gray or no hair and a coronary in your early 40-50's. I see too many green newbies fresh out of college all excited about security and their careers. I don't know if I should find them amusing or scary. I guess someone has to do that job.
As for me, If I can keep learning and enjoying what I do, I couldn't ask for anything more.
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
Actually, it is older that Dilbert, and used to be known as the Peter Principle. In short form it stated that as long as people could manage their jobs, they got promoted, so everyone ended up on a level where he could not manage his job.
"support; some networking; DBA; web development; project management; even working on the client side"
.NET enterprise software engineer, with solid proficiency in SQL Server 2000 and 2005 -- at a large company with a variety of dedicated resources, I wouldn't call hire on as a DBA, but at a small or medium size company, I would feel quite comfortable doing so. I can hack my way through server and network administration, but mostly in a development role -- I wouldn't sign on as anything more than an entry-level role in server or network engineering. (And I wouldn't even sign on for entry-level, because software is where my heart is at.)
These aren't fields. They're roles. They're roles that will always play a part in IT. As others have mentioned, you should focus on what you like. At the same time, don't become overly-specialized -- if you pigeonhole yourself, you risk your job security in the long run.
Personally I'm a
"Web development" has become a silly term. Be an engineer, know the technology, and desktop vs. web won't make a difference. Be a "tech," and again, you're pigeonholing yourself, and putting long term job security in the pooper. Make sure you're proficient in current technology, but keep an eye to the future. Attend user group meetings. Attend industry conferences.
You shouldn't base your future on specializing in one of these roles you've specified, unless that's what you want to do, and nothing else, ever. You're better off exploring theory, being capable of applying practice. Improve your communication skills. Learn something new every month. Read the Pragmatic Bookshelf series, I think they might help enlighten you. Read well-known works, the classics, the new hotness. I can't say it enough: don't pigeonhole yourself.
I am, therefore you think.
Somebody's bitter.
... or, rather, my car.
I was bitter once. I got laid off after 9/11, couldn't find a job to save my life
You have to bounce back -- if you don't, you shouldn't be in the field to begin with. Same thing applies if you can't find a job today -- you probably need a new profession. IT is booming, the Internet bubble was a temporary setback. Not all IT is INTERNET.
Not everything can be offshored -- I've seen successful offshoring, but I've also seen a large number of disappointed businesses who feel they were overcharged for sub-par return on investment in off-shored projects.
There is always a need for business analysis and system architecting. Someone thousands of miles away is going to have a very difficult time truly knowing a business, and understanding its needs. There is ALWAYS going to be a need for capable, creative people who know the technology AND the business to be local.
I am, therefore you think.
Amen to that. Far too many businesses promote someone to management because 1) they're been there for a long time and 2) they're good at their technical job functions. They don't, however, have a lick of personnel or project management skills. It also usually ends up taking someone from a job they do well and putting them in a job they do poorly, a double whammy. I'm at least smart enough to know that I shouldn't be given anything beyond a team lead position.
There is a difference between "insightful" and "inciteful" other than spelling.
"Be an engineer, know the technology, and desktop vs. web won't make a difference.
It makes a difference to every HR person.
The Kruger Dunning explains most post on
Go with the job that you LIKE. Not what is the best for a career.
A career in which you don't feel at home with will kill you before you get to retirement.
Based on job postings on various popular tech boards: 1. SAP 2. .NET
3. JAVA/J2EE
Reports of every IT job in the US moving to India have been greatly exaggerated. Indian salaries have been experiencing double-digit growth over the last decade and are now reportedly 50% of US salaries for similar positions. I predict that in the next decade there will no longer be a compelling business case to offshore all but the largest development projects.
I'm manager of a couple of teams at top 5 bank, and my team is primarily responsible for data warehousing and ETL processing for the mutual fund division. Frankly, the best position in IT is the job that is not easy to acquire offshore, and pure IT is... I can find .NET or Java engineers both in the states or overseas; I can find sysadmins here or offshore; and while the requirements rigor is much higher for offshore resources in a development context, I can get it done cheaper, as unpopular as that may be on this board.
Most IT folks don't work in a pure IT shop, ie - Google/Oracle/Microsoft - essentially a company where the technology is the product/service offering. We are enablers of some other business, and at least at my company, we are offshoring like mad so every new development position gets weighted against a set of criteria to see if it's offshore eligible: unless there's particular industry and/or business data knowledge, they typically are eligible.
My recommendation - learn the business. It's the hybrids that companies will retain in the future. It's the blend of business expertise and IT solutions that is difficult for an organization, hell, even a manager, to replace. A specialist here is truly just a commodity worldwide without the corresponding industry and/or business expertise.
I disagree. I'm a "jack of all trades, master of none" and I'm well paid. That means I'm pretty much stuck in my job unless I want to take a huge paycut.
It started off as a specialty position (graphics), and I was well paid for it. But it turned into a position where I was responsible for a lot of other, varied things, like the intra-departmental website, and eventually my grasp of modern graphics technologies started slipping.
Now, because it started off paying so well, I'm still paid well... but now my raises are crap, not enough over cost of living to make any difference. I while I like the company I work for, I hate the location, and would take an equally paying job (adjusted for location) just about anywhere else.
The problem is that when I look at available jobs, the ones that pay even moderately close to what I'm getting now require a specialty.
This really kills me - because I'm sure I could get a great raise here if I threatened to leave, but I wouldn't threaten to leave unless I could follow through on it (I'm not good BSing with empty threats).
So, OK, I'm giving my annecdotal experience, but I find it's true elsewhere. I've had this conversation with my manager and he agrees, and he'd like to see me be able to get back into graphics 100% of the time, but the company won't budget for another programmer (I'm in a unique position here). I like all the things I'm doing, but I wouldn't mind dropping the variety and concentrating on being great at one or two things, I'd still be happy and I'd be able to demand more at a different place.
Stupid sexy Flanders.
I would expect the ones with the most job openings would be the "hottest" jobs.
Not as much as you'd think. A good portion of openings I've seen there are from headhunter agencies that put up phony jobs for clients that don't exist. This gives them a pool of resumes to boast to their own clients about.
Out of all the career books I've read, Ask The Headhunter is the one that struck a chord with me. His take on Monster/Careerbuilder, while old, still holds true.
Where does the school board find them and why do they keep sending them to ME?
For instance I was working as a developer for an advertising company doing PHP, Perl, Linux, Javascript, etc where I live now. When that job dried up I needed to find work in my area but 90% of what's going on in Baton Rouge is in the Microsoft environment. I couldn't find a job for quite a while because I didn't have 2+ years of Microsoft development.
I got plenty of job offers out of state(for some reason Tampa Florida companies like my resume) but nobody around here.
So I purchased a few .NET 2.0 books and learned enough to talk my way into a position. Working with Microsoft development is ridiculously easy for me. I can't believe I had a hard time finding a position because I'd done non-Microsoft development but oh well.
Location is extremely important. I'd definitely take a look at what's going on where you want to live before you take a career focus. Now that I've been working with .NET I feel pretty secure that I could jump from opportunity to opportunity if I needed to.
For some reason I refuse to use either spell check or the spacebar properly.
Actually, I beleive the Dilbert principle is more accurate in the GP case : "The least competent ones are promoted first to take them away from productive position where they could be dangerous".
From what I've experienced again and again and again is that one of the reason (and there can be others) that techies don't make good managers is that they try to live in both worlds. The new techie manager still wants to get his hands dirty doing the day to day work. Part of this is that they are don't trust others to do it "right" or they are afraid of losing their technical skills. The new techie manager never really gives him/her self over to the dark side of management.
Indeed, the real Dilbert principle is that people get promoted to a position of power *because* they are incompetent. Reasoning is that they do less damage there.
http://dilbert.com/comics/dilbert/archive/images/d ilbert2007048874323.gif
Jobs in the finance side of IT are, and will, remain very strong. Jobs such as "quant developer" that combine strong IT skills with business knowledge will always be in demand from investment banks and other financial services companies. These roles involve C++ and VBA development plus quite good mathematical skills to be able to understand and implement the pricing models but if you have the skills you can get the money, one thousand pounds sterling per day in London at the moment if you're really good..!
In 1987 I started working full time in IT (plus some part-time IT jobs before that). Two MS degrees (one in statistics, the other in CS). I'll make $83K this year.
My 23 year old nephew graduated from college last year, majored in marketing. He just got promoted and will make $85K in salary (bonus could put him into 6 figures).
If you want "Hot" because of the bucks, IT might not be the way to go.
I just can't get my hair pointy enough to do it.
It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
A lot of people disagree with me, but if you want to stay technical, chasing the latest specialty is not always the best way to go. If you really want to build a technical career that will last you through outsourcing, technology shifts, etc., then you need to have a broad background.
:-)
Smart people will always find work. I've bounced all over the IT world...support, sysadmin, design and architecture, and it's really hard keeping your skills truly sharp. Someone who's truly valuable picks a few key areas to get really good at, and knows _something_ about the rest. If you're a network guru, learn a little about the machines you're connecting. If you're a systems genius, learn enough about databases to realize your DBA is BSing you.
Take the latest fads...SOA and security. You can learn everything about these two areas, but what happens to all that knowledge when it becomes a commodity? When the execs realize SOA is just a rehash of centralized computing with some XML and the web thrown in, where will you be? Keeping yourself open keeps you employed.
I learned through a really tough experience that management was not for me 2 years ago. Technical people generally don't make good people-managers. It's not lack of social skills, but management is a completely different job. You will never touch a machine again. You will be in meetings, answering e-mails, making phone calls, and "separating the kindergarteners" when they get into conflicts. If you burn out on technology, then it's an excellent career path. Otherwise, don't let people convince you it's a good move. Rememeber all the bad bosses you have/had? Just like some people aren't suited for IT, they're not suited for managing either.
One good overspecialization example I like to cite is OpenVMS system administrators. OpenVMS is still in active use, but it's really declining. Truth is, it's easier to write new applications to run on Linux/Windows Server than to pay for expert system administrators. One of the first IT jobs I had before moving on was VMS support. I don't know how DEC trained these guys, but they're some of the best, most vigilant admins I've ever seen. However, finding a paying job working with those systems is getting harder. I world love to have that kind of sysadmin in the Linux and Windows world I work in, but a lot of them are totally specialized and don't want to learn new systems.
One other thing...outsourcing is here to stay. If you're a developer, become a crack genius developer so you can get the contract jobs rewriting outsourced code that doesn't work. If you're a procedural system admin, become an operations wizard that designs systems that don't randomly blow up. In short, truly earn your money!
Small shops *love* jack-of-all-trades because they have to be able to cover a lot of bases without specialized help. I've worked of academic and government agencies where they had limited budgets to hire many people so I had to dabble in DBA, Unix Admin, Apps Admin, Developer, User Support, etc all at the same time. I never became a master of Unix admin tasks (big hardware changes justified getting some help) but now I know enough to understand other specialists. My DBA knowledge alone is very valuable for performance recommendations or simply knowing when to say "This is a DBA issue, not a code issue". Even when you work with a group of specialists you quickly become important if you have a broad base.
It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
When you hire someone to program for you, communication is absolutely crucial to success. If the person you hire doesn't speak the same language you do (or doesn't speak it well), you're probably not going to get what you ask for. Also consider how bad communication will be if you are unavailable (sleeping) most or all of the time they're working. You can only communicate once per day. If they have a question, they have to stop working until the next day when you've answered them.
A good portion of the time, outsourcing is just not worth it. It doesn't matter how cheap the labor is, when the product you end up with is not what you want.
The company I work for expects managers of technical folks to keep doing tech work themselves. As a result they don't manage well, and their tech work suffers too. The corner office folks think managing techies is not a full-time job, and want to get the most for their money. But it's a completely short-sighted policy. We did hire one guy who was an excellent manager, and only did management though he had an engineering degree. For a year his projects were consistently on-time and under-budget. They fired him. Said he wasn't producing enough specs and code.
Hur man än vänder sig är alltid ändan bak
First of all I will say that I have worked mostly in software development in my career, although I also have some UNIX system administration experience in my background. Because of that, this is focused mostly towards software development although some of it applies to other IT functions as well.
Next I want to clarify my own personal definitions. I define Information Technology (IT) as the group that provides technical expertise to a company in order to support their business needs. For example, if you work for a bank, you maintain the computer hardware software that allows the bank to make a profit by providing financial services. You aren't really directly contributing to the bottom line, since you aren't creating a product or service that the bank sells, but you are critical to their success.
The flip side of that would be Software Engineering or Technical Consulting, where you work for companies like Oracle or Microsoft or IBM. Although those companies have IT departments, the positions I'm referring to are the ones where you produce a product or service that is sold to customers to generate revenue. In this case you ARE directly contributing to the bottom line.
What I see in the industry is less of a demand for actual software development in the corporate IT world. In the past, companies needed a software development group, because they developed all their software in-house. If you worked for a tire manufacturer, and your company needed an accounts payable system, you would often develop and support it yourself. Now, that same company would be much more likely to purchase an ERP suite like SAP. If you needed needed technical customization, you hire consultants and/or contractors to come in and do the work on a project basis.
This is also true of help-desk and even networking/system admin functions. We're seeing more and more of those commodity-type positions being outsourced to third-party providers, especially in larger corporations.
So... my advice to someone just starting out in IT would be similar to what has already been said. If you really want to stay technical and go into hardcore software development or system administration or something, try to get jobs with companies who make that their focus, or else be prepared to work as a contractor or consultant, traveling frequently from project to project.
However, if you want to truly be successful in corporate IT, try to get as broad of an experience base as possible. Ideal IT candidates in the future will have broad experience in both hardware and software, and also the communication and people skills to help leverage technology to solve strategic problems. Working in the IT department of a big corporation will mean that instead of writing that accounts payable software package yourself, you will be identifying the requirements and coordinating with the different vendors to get the job done. You will still need technical knowledge, because you will have to be able to communicate with the consultants/contractors/vendors, and you will performing the integrations between the systems. However, you might not be slinging code all day.
Just as a disclaimer, I will repeat that this isn't a 100% rule. There will always be a need withing corporate IT departments for software development, because companies will always develop creative solutions to give them a competitive advantage over their competitors.
If you're just starting out, my recommendation is try several areas of the technology field and figure out what makes you happy. Being happy in your job is much more inportant than just money, in my opinion. If you don't like what you're doing, try something else. Having a broad experience base can only help you in the job market of the future.
I've had a pretty successful career, totally by accident, so here is my advice.
.net or Java? Are the more jobs available for an Oracle DBA or a Microsoft SQL DBA? If that is your primary consideration then you will probably be beaten out by the people who are passionate about their career choice and made it for other reasons. Honestly if you are really excited by databases (you sick bastard) then you should be interested in working with all of them and learning as much about both DB theory and the specific implementations as you can.
Do what you enjoy. That's it.
Everyone I know in IT who really enjoys what they do (to the point where they would probably do it as a hobby for free if they were independently wealthy), ends up being successful. They are passionate and competent, likely not because they are inherently smarter than anyone else, just that they spend more time learning, experimenting, and playing around with the technology they like and work with.
I also know people who picked their IT career (and decided to go into IT to begin with) based solely on the job market. Will I make more money with
There are jobs out there for everything. If there is something out there that really gets you excited go for it. If you learn quick, really throw yourself into it and know your stuff, you will find employment. It might be more lucrative in the short term to trend hop, but if all you are interested in is the possibility of making big bucks then you should forgo IT and go into something like hedge fund management.
Me? I really dig identity management stuff. I've worked in academia with SAML, Kerberos, and PKI and in the corporate world with Oracle and Sun's IdM tools. A word of warning though: Find a field you enjoy, but do not get too hung up on a specific technology. I'm happy using my knowledge and experience in IdM to work with Infocard, SAML, PKI, LDAP, NIS, Xellerate, CoreID, Kerberos, AD, etc. I have my opinions as to what is best for what need, but I try to not be too much of a snob about it and limit my career that way. I've seen a lot of people go the "horse and buggy" way by latching on to a specific technology and refusing to let go when the world moved on.
Finkployd
Jack of all trades,
Master of none;
But oftentimes better
Than master of one.
End users are becoming more savy, and as such, while there is still a large market for desktop support, salleries are lower now, because you have so many techs right out of high school that can do the same thing.
.NET, ASP, SQL, Pearl, Python, and C? My company is hurting for skilled Python developers, and we pay a pretty penny for them.
Get your MCSE and Cisco Certifications, and go for networking. You will be treated like crap, expected to work extended hours without the benefits of overtime pay, but you will secure yourself a job.
Focus less on webdev. Focus more on application and Intranet dev. HTML is being taught in gradeschool, most high schoolers can do Flash and know how to use photoshop, but how many do you know that know
Just because we all love Linux inside and out does not mean that everyone uses it. The last few companies I have worked at have been Microsoft houses, and now I work at a company that also has some Apple stuff. Make sure you know your Windows Server 2003 and Apple XServ
The new techie manager still wants to get his hands dirty doing the day to day work. Part of this is that they are don't trust others to do it "right" or they are afraid of losing their technical skills. The new techie manager never really gives him/her self over to the dark side of management.
You see, that IS the real "dark side" of managment -- when you become a micromanager or some other type of manager that constantly second-guesses their employees because you "know better." Even worse is the type that is constantly trying to make people prove themselves to them by withholding information to see if their subordinate is "smart enough" to come to the same conclusions (and then berate them if they don't either due to a difference of opinion or a crucial missing piece of information).
I've had four jobs since I entered the IT field. Every single manager I've had was a former programmer with the exception of one boss's boss (who was entirely awful because she was more interested in office politics and backstabbing for advancement... but I digress).
All the good bosses I've had gradually abandoned the programming side and learned to act as mentors. They used their knowledge of the system to give pointers on where to look when you were stuck on a problem and trusted you to get things done, only prodding every now and then when a schedule was threatened. All the bad bosses I've had (save the one mentioned above) second-guessed you constantly and either went around your work to put someone else on it (like themselves) or constantly made you justify ever single moment you spent your day on. In both cases, the attitude comes from the thought that they could do it better if they didn't have to do all this management crap instead.
In other words, the secret to going from a technical role to being a good manager is learning to let go. Use your skills and knowledge to aid your subordinates and shield them from upper management by understanding what they are doing. If necessary, use you knowledge to call their BS if they're actually slacking, but don't envy them or treat them as irritating time-wasters blocking you from doing "your real job." Otherwise, you're just demonstrating the Peter principle.
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
Small shops should and do love JOAT folks, but they may have trouble hiring them.
If a shop is large enough to have an HR department (complete with screeners) it's hard to get a foot in. It's often difficult to get a position open to hire for with the designation Jack of All Trades. Uppers don't understand, and HR certainly doesn't. (Thats a common situation, but not a rule.)
If they do get that designation, starting salary for the job will be somewhat low, because that designation will be of lower status than an "expert".
And small shops tend to pay less than big ones in the first place.
This wouldn't apply at all for a shop consisting of just one or two people, but then, they tend to pay VERY low salaries.
For the record, I'm a JOAT, too, but have been involved in a bunch of hiring.
You may become obsolecent in the technical sense but if you are a good manager you can avoid falling behind in the management of technology or sw development or whatever. The real risk is simply there are a lot fewer managers than rank and file developers, so there is a lot less demand for them.
It turns out these are really different skill sets - one set cranks out code, the other set knows metrics, process, etc, still technical but not the things most rank and file developers obsess over.
That being said the main requirement for being a good technical manager is still being a good manager. I've had managers who had no technical skills, but the ones who knew how to evaluate, metricize, and develop processes specific to the task at hand were better.
Give a man a fish and you have fed him for today. Teach a man to fish, and he'll say "WHERE'S MY FISH, YOU IDIOT?"