The Future of IT in America?

tomocoo asks: "As a young person considering various choices for the future career I'd like to pursue, IT and computer science continually reappear near the top of the list of fields I'm interested in. In fact, one of my only hesitations is the suspected ease by which programming and other related tasks can be sent to other countries for pennies on the dollar. How much of a threat do the readers of Slashdot feel outsourcing is to the American programmer? Should I and other young people be pursuing something more specialized or have I simply been watching too much CNN?"

Comments

There will be a job for you

[dracocat]

I have been hearing about the doom of the industry for a very long time. The fact is, is that IT and Computer Science follow a cycle.

Will there be a high paying job waiting for you the moment you graduate? That is impossible to predict, but long term you are almost assured to find a healthy career waiting for you.

Proof that the offshoring is an overexagerated issue? Look at average salaries of graduates. They may not be as high as you want them, but compared with any other fields they are consistently towards the top. Even now, with so much media attention focusing on the downturn in the tech economy, I doubt you would receive very much sympathy for having to receive a starting salary of over 51k. (Starting Salaries)

Anyone complaining about the lack of jobs and low pay in the industry is an anomaly. I am not saying it is their fault, but there will be people that simply have bad luck finding a job no matter what field you look at.

In short, the reason there is so much noise is simply because some people have unrealistic expectations of both finding a job and the pay they will receive. Take that away and what you have is an industry on a whole that is actually more healthy than a lot of others.

All of that being said, it is always better to specialize if your goal is more money. Almost any job will base your pay based on your expertise in the area they are looking for. If a job is looking for a C# developer and you have a little knowledge of everything then you will get paid for having a little knowledge of C#. If on the other hand you are a Java expert and have been doing nothing but Java for the previous 5 years you may not get that C# position at all, but when you find a company looking for someone with knowledge of Java you can definitely expect a higher pay.

Re:There will be a job for you

[mcrbids]

I'll be glib. I'll be gleeful. And I'll be right.

Make your own damned job. It's the American way. Start your own business, hang a shingle, make some sales, do some cold calls. It hurts at first, contracts don't come with a 401k. But, pretty soon, you get the whole customer-relations thing figured out. Then, not too horribly long after that, you get the whole tax/accountant/bank thing figured out.

Next thing you know, you're swamped with highly paid work! You've stretched your wings, you've gone out, you landed a few key contracts, and suddenly, you have more work than you can do.

So then you figure out hiring and firing. It's a painful lesson, as you often really like the people you're firing. It can be very expensive, if you miscalculate and pay people to make up stuff to "look busy". But, if you come even close to getting it right, it pays, too, and sometimes quite nicely.

If you're half as skilled as you make out to be, you can follow this path, and make better money than your graduate peers in as little as 5-10 years. You can be independently wealthy (retired, never work again) in as little as 20 years.

That's the American way.

Do you want to be the kind of person who mopes when you can't afford your own private plane for at another year? Do you want to be the kind of person who ends up paying more in "recreation" than most people earn in their jobs? Do you long for the stability of knowing you can never be fired, because you're not only the boss, but the owner of the business?

Take your skills, and find a way to market them. A business license costs around $50 in my home town of Chico, CA. A fictitious name statement and accompanying bank account can be had for around $300 most places in California. Everything after that is up to you.

When you take the time to dissect business models to see which works for you, you grow in ways you can't easily convey. When you shoulder the responsibility of keeping the show running, even when your cashflow is bleeding red, you become a bigger, more capable, and more powerful person. When you run the show, you become a bigger, better, more capable, more responsible person in ways that years of college can't even begin to approximate.

I strongly recommend that you turn your frustration into success, and turn your own personal lemon juice into sweet, refreshing lemonade!

Once you've done this, the whole idea of a "job" just seems... well... stupid...

Re:There will be a job for you

[Michael Petrov]

I completely agree with your take on this job "crisis" - and I am an actual example of how it can be done!

I had a passion for programming since I was 10 years old and as other posters have said, that makes all the difference. I have been working independently in the industry for only a year now - my work consists of a wide variety of programming: C++ development, web programming work (PHP / MySQL), and other programming related work. At this time I do not have a formal education and I was never even asked for it throughout my relatively short career - when you independently do contract work, credentials become irrelevant. Starting a year ago doing a lot of monkey programming to increase my actual programming skills was a great way to learn the new technologies and gain practical experience, the pay was at that time relatively low ($10-$20 per hour). It has then grown into more interesting work, and now I'm getting consistently paid $60 / hour and more.

I am not implying that this path is easy to take: there are countless late nights, constant weekend work, and it's at times interfering with my studies. MY point is that it took some effort, but my passion for programming did the rest. I am constantly developing my own side projects to gain passive income, reading marketing books, and improving my investment skills. I am proud to say that I accomplished all that between the ages 16-18 - so my advice for the original poster would be to take action and start a business. I am currently 18, therefore in September I will be going into a top Canadian University for Computer Science. I decided to try getting a formal education - I am not going to University to become employable, but merely to gain some new knowledge and take many business courses. Therefore working in North America within the CS industry can definitely be done - but you have to become the one outsourcing the work or hiring local workers.

Once you've done this, the whole idea of a "job" just seems... well... stupid... I completely agree with your take on this - currently all my peers are being brainwashed to "get an education and a safe secure job". When I hear that line, especially combined with job stability - I merely laugh and take note of who could be employable for a minimum secure wage. If you want to live out "The American Dream" - then just do what other great people did: work hard and learn skills in all areas (accounting, investments, programming, selling, marketing).

Re:There will be a job for you

[FredFnord]

I'll be glib. I'll be gleeful. And I'll be right.

Glib, and gleeful. And right for you. And a bit, sorry to say it, self-centered, because you assume that something that would work for you would work for anyone. There are people who are comfortable doing this sort of thing and people who aren't. And if you aren't, you're not going to succeed at it. And of course, the possibility of doing this sort of thing depends on not too many other people doing it.

Make your own damned job. It's the American way. Start your own business, hang a shingle, make some sales, do some cold calls. It hurts at first, contracts don't come with a 401k. But, pretty soon, you get the whole customer-relations thing figured out. Then, not too horribly long after that, you get the whole tax/accountant/bank thing figured out.

If you're lucky. And you're cut out for that kind of thing. And you're lucky. And you're not in a market that's oversaturated with people who can do what you can do. And you're happy to work fifteen hour days, seven days a week, at the beginning at least, because that's what it's going to take to satisfy some of your more demanding customers. And you have enough money to get you through the first year. And you don't accidentally alienate your first employer though not doing something they assume you will know to do, because you're not experienced. (Pleading inexperience doesn't work; they only want people who are experienced.) And you don't get a company that signs a contract and then doesn't pay you for eight months after you finish the job, when you can't really afford the time and money to sue the hell out of them. And you don't get companies that make you give them a cost up front and then continually add features while you're working. (I lost two clients that way, because I told them I wasn't going to put in extra work that wasn't in my contract for no extra money, and they said, 'Well, then, I'll find someone who will.')

And the sorriest thing is, you only get a chance to run into those problems at all if you're lucky, or at least not unlucky.

It's really the smugness and superiority that drive me nuts. 'It was right for me, obviously it's right for everyone!' I've tried it. It's hard, it's nasty, and it's not a situation that fits every personality type. I made it okay for a couple of years, but I was delighted to return to a job where I was working 40 hours a week for decent pay and had health insurance that couldn't be cancelled (three times) for no reason other than a single, low-cost, low-mantenance health problem. I like to have a social life that doesn't require me to choose between it and sleep on any given day. I like to have coworkers to interact with, and to ask when I have a problem, and to go out to lunch with. And God, do I hate billing.

Perhaps this is the business model of the future: work 15 hours a day every day with no health insurance and no guarantee that you'll actually be paid before you starve to death or else you won't have a job at all. If it is, I will probably live through it for as long as I decide it's worth living through. But don't try to sell it to me as some kind of goddamned paradise because I know what hell looks like.

-fred

Yeah, too much CNN

[RunFatBoy.net]

You're way too caught up in picking a career by the "current market trend". If you're great at what you do, there will always be a market for your skill set.

If the current trend of outsourcing has you scared, what about other adverse situations? What about the next recession; are you going to run back to school and become a CPA? I'm suspect that you have a deep love for programming. When you love development, you feel it in your bones; you think about problems on your lunch break, you stay up until 3am to get that last bug worked out. If you don't have this sort of passion for creative logistics, then maybe you should reconsider other options (because you're likely to get burned out fairly quickly).

Jim http://www.runfatboy.net/ -- A workout plan that doesn't feel like homework.

Re:Yeah, too much CNN

[Stiletto]

If you're great at what you do, there will always be a market for your skill set.

Tell that to the great buggy-whip manufacturers.

Re:Yeah, too much CNN

[rolfwind]

I don't know, they might have switched to BD/SM products;)

Up, not down

[Marlow the Irelander]

As I understand it, IT employment in the US is increasing, not decreasing; you'll have a better chance if you develop skills in things like project management rather than just being a code monkey.

Re:Up, not down

[GoofyBoy]

As the AC clearly points out, you need more than just coding skills to stay employed. You also need interpersonal skills.

Young People.

[sglider]

I am one of those young people. I'm finishing up a stint in the Army, and going back to finish my final year of my BS in Computer Information Systems. ( I was mobilized during my senior year of college.)

I firmly believe that there is plenty out there for me -- but not in something like programming, rather I believe my talent lies in being a Systems Analyst for a business, or something both technical and managerial in nature.

Sure, the off shore folks have us beat when it comes to programminng, no doubt about that -- but that's only a problem if you want to be just a programmer.

They still need people to lead and manage these teams of programmers, and perhaps that's where the value of the American IT professional is.

Re:Young People.

[ClamIAm]

Sure, the off shore folks have us beat when it comes to programminng, no doubt about that ...

Sure, managers and PHB-types might think it's a great idea to outsource programming. By doing this, you can get a similar-quality "product" for a much lower cost. But it's not all roses and cherub farts.

Programming is hard. There have been countless times where a project has not met the needs it was supposed to, and this often has to do with poor communication. Now throw in a few thousand miles difference from the customer and the coders, a time difference and possibly a language barrier. Is this going to make it easier to get what you need? The chance for miscommunication here goes up a huge amount. What also gets worse is turnaround time. The factors I've mentioned will definitely slow down some parts of the development.

Re:Young People.

[El Cubano]

I am one of those young people. I'm finishing up a stint in the Army, and going back to finish my final year of my BS in Computer Information Systems. ( I was mobilized during my senior year of college.)

You have a couple of serious advantages that your peers (other recent college grads) simply don't have:

• Employers know that you are disciplined (that is a given based on military experience)
• They know you are already well trained (it doesn't matter at what) and apt to learn since you had to go through a good amount of training for your MOS (unless you happen to be a cook or truck driver)
• You probably have a security clearance (even if it is just a Secret-level clearance)
• You are probably more mature (in terms of age, where the people graduating with you are likely 22-23 years old, you are probably 25-26 years old), which makes a difference in how potential employers view you

In summary, you have nothing to worry about. Same with others in similar situation to yours. The moral of the story, if you want to be better off in the job market, consider a 3-4 year hitch in the military. Even if you are not in IT, the added experience will be a huge benefit and establish a track record that you can show to future employers.

If it's what you want to do, do it.

[deanj]

Don't worry about what CNN is saying. They're not programmers. If you're a decent programmer, you'll always have a job.

Here's the bottom line, though:

If programming is something you love to do, then do it. If it's just something you want to do because you've heard it'll earn you "big bucks", don't.

Not that you can't make a good living...you can. It's just that unless you love something, you shouldn't go into it. You might be able to handle it for 10 or even 20 years, but unless your heart is really into it, you'll regret it long term.

Good luck.

Learn what you're good at.

[crhylove]

And you'll be useful to somebody. Get really good at something, and you'll be useful to everybody. Almost doesn't matter what field. Whatever it is you REALLY enjoy, there is a way to make money at it, and a way to make yourself valuable in that field. In fact, if you REALLY enjoy it, create something new and market THAT. That's the way to make real money. I don't know anybody who makes a lot of money solely based on their education credentials. I'm sure they exist, but that breed is becoming rarer and rarer.

rhY

Outsourcing

[Metabolife]

Most of the programmers I see working in the US have something to go along with the CS major. Having an english degree with the CS degree, for example, makes you multifunctional and can specialize your work (real world example).

You don't want Computer Science

[Heretik]

if your primary concern is writing software and getting a job making money doing so. You want Software Engineering.

I suggest you do some research into what Computer Science actually is before assuming you'd like to go to University for it, because if you think you'll spend the majority of your time programming, you'll be unpleasantly surprised (The obscenely high first-year dropout rates of Computer Science programs are due mostly to this misconception)

Re:Learn a new language?

[Keruo]

Parent was bit trollish, but he has a point though..
Asia is currently worlds fastest growing economical area, and knowing how to speak japanese, mandarin or hindi might be rather useful.

Sigh

[NitsujTPU]

Do this with your future: What you want to do with it.

Do you really feel so tied down that you have to choose your career based on current trends? The trends won't last through when you finish your degree. Do you think that people who started their BS during the dot com boom made a dime of the millions that people made hawking their crap?

Seriously, pick a career based on what you want to do. You'll be a happier person for it.

There is shortage of good talent in Silicon Valley

[cryfreedomlove]

I am a hiring manager in Silicon Valley. There is a shortage of great talent among the IT work force. In the last 12 months it has gotten harder to hire great talent and there is a definite salary inflation situation going on right now because most great candidates are seeing multiple competing offers.

Do IT only if you love it.
Consistently renew your skills. Commit yourself to a lifetime of learning new tech.
Live where the jobs are (e.g. San Jose, CA or Austin , TX).
Find a business where you are excited to apply your skills.
Avoid arrogance and treat people well.

Do these things and you'll always be in a high paying job.

Don't worry, go for it

[LowneWulf]

I wouldn't worry. Sure a lot of even development tasks are being farmed out to India or China. But there's still more than enough demand and competition for the top CS graduates to ensure a healthy and lucrative career.

My only advice is to get a good education, and build a good resume while you can. If you spend 6 months getting a certification-of-the-week, write a little text adventure in Visual Basic, then wonder why you're not getting six-figure salary offers to start, you're probably next on the list to be outsourced. If you've got a CS undergrad degree (or better yet, a master's degree) from a top school, then people are going to be literally fighting over you, and I don't see that changing anytime soon.

Make sure you can write.

[daeg]

The best advice I can give you is have stunning writing skills. You will be writing every day. E-mail, IM, proposals, agendas, reports and presentations are part of any job, even if they are a small part. Some companies don't care if you have good writing skills, but no business will complain if your skills are higher than they want.

Media spreads fear, uncertainty and doubt

[Mustang Matt]

The offshoring problem is grossly overexaggerated and all it does is separate the men from the boys.

That being said, I would focus on doing something you enjoy regardless of money. It makes the difference in life. I bet a lot of people claim to enjoy their job on here, but I bet a lot of them are lying about it. Usually the money makes these jobs worth tolerating but working in a "the office/dilbert/office space" style environment is detrimental to the soul.

don't do information systel.ms

[Gramberto]

Computer Science, computer engineering, and electrical engineering are far more powerful degrees. They are also much hard than IS. I took some IS classes to learn some new things at a local state college. I thought the classes were a joke. The classes were easy. There was no low level theory at all. No you will never directly use the theory, but if you understand the concepts its much easier to grab a book and learn the practical stuff on your own. The same school has very hard computer science courses.

Even if you want to be a network engineer. You will learn ALOT more with a computer science degree. You can then do a minor in information systems and take a few classes that you are interested in.

Computer engineering is probably the most valuable to employers. The reason is that the barrier to entry is higher. For a network administrator or a programmer you can learn it without school. You really can't learn computer engineering without school.

Re:don't do information systel.ms

[joekampf]

No, most of us with our CS degrees are not creating the next processor, or the next programming language or OS. However, what I have found to be invaluable, and what makes ME more valuable than the masses of IS majors or even the offshore/inshore cookie cutter programmers out there is that I understand what is going on under the covers. So when I decide to use a feature, or create a system, I'll know how it will scale, what the implication are when the damn thing is running on something other than my desktop. I can't tell you how many developers out there have no idea about things like, threads, transactions, I/O, networks. What can go wrong when those things break or are not handled right and what that means to the system they are developing. Thus you get crap that has to be restarted every day, or isn't robust.

Career choices

[bytesmythe]

I've noticed a number of problems with IT as a career choice. Back in '97, I graduated with a degree in computer science and started working like everyone else. I hopped from job to job for a number of years. The longest I stayed at one place was about a year and 4 months. After a while, I finally realized my problem. I absolutely hate working in IT. There are a number of reasons why. I'm not saying that these will apply to you or anyone else, but if you feel they do, it might be a good indication that IT is not the field for you.

1) I can't stand having to work on other people's stuff. I don't like being given assignments that I'm not interested in and having to complete them. I'm sure people with stronger "work ethics" can force themselves to muddle through, but I'm not going to do it. Worse, there are a lot of mundane administrative tasks (like timesheets, etc.) that have to be dealt with. If I'm working for myself and getting paid based on those things, it would be different, but it always just seems like a waste.

2) Having to constantly keep up with new technology got kind of old for me. I like low-level programming in C. I don't really care for web apps and such. I tend to find the various frameworks overly complicated for no apparent reason. Most places I've interviewed with want to see lots of solid job experience with particular technologies, which can be difficult if you weren't working somewhere that used it. .NET is the newest example I can think of.

3) "IT" type programming isn't very interesting. I would rather work on low-level stuff, simulations, academic problems, etc. I don't really care a bit about data migration, or making loan payment GUIs, or whatever. There's relatively little problem solving to be done, which is the whole reason I liked programming in the first place. Instead you get handed some half-assed specs and spend all your time chasing people down to figure out what needs to be done, even though none of them really know or have the authority to decide. That's when the meetings begin.

4) Did I mention meetings? I hate meetings. I can't decide if conference calls are worse or not. On one hand, you can mute the phone and make faces, but on the other, it's frustrating to have to listen to people you can barely hear, deal with flaky connections, etc., and you still have to pay attention because someone will certainly end up asking you a question.

5) Outsourcing. Not just to foreign countries or migrant H1-B visa holders, but to any third-party contracting group. There are several problems with this. Many times, consulting companies (Accenture) will put people on a project who have never programmed before. They don't even have degrees in programming. The consulting company will use a project to train them. It's real fun explaining what recursion and stack overflows are to someone on a major project.

6) If you ARE a contractor though, you might be in luck. You're more likely to get to work with newer technology, so it's easier to stay ahead of the curve. From what I've seen, full-time employees tend to have to work on maintenance rather than new development.

Right now I'm transitioning out of IT as a career. I'm still working, but as a training consultant. It pays enough that I can finally risk going into business on my own. (A non-IT business at that!) The only way I'll ever feel motivated to put effort into a "job" is working for myself. I'll never give up computers and programming, and will pursue it as a hobby (and possibly as an academic career in the future) for the rest of my life.

But work in IT in the modern business world? No way.

Re:Career choices

[Kjella]

1) I can't stand having to work on other people's stuff. I don't like being given assignments that I'm not interested in and having to complete them. I'm sure people with stronger "work ethics" can force themselves to muddle through, but I'm not going to do it. Worse, there are a lot of mundane administrative tasks (like timesheets, etc.) that have to be dealt with. If I'm working for myself and getting paid based on those things, it would be different, but it always just seems like a waste.

That sounds like working in any reasonably sized company in any position. I think you will find that even working for yourself you have to do a lot of work that isn't interesting, but the authorities or your clients demand it. Timesheets are annoying to track in any case but unless you track time and see which assignments are winners and losers your business will fail quite quickly, not to mention you normally need it for invoicing.

The rest of the points are fairly on target, but if that's your 1) reason to quit, good luck. My experience is that the grass isn't greener on the other side. I went from being independent (co-owner) to working for a major company. Why? I know what my paycheck will be, it's not stellar but it's predictable. I get to do more of what I want to do - in a small company everyone's a handyman where needed. And at the moment, I feel a slowness in work is more my boss' problem than mine, because I know I have specific skills they need and can't make anyone else cover for. I could imagine trying to make it on my own again, but then I want to have what I consider a sure-fire winner. Going out there again just to have all my clients be my "boss" instead of the one I have? No thanks. It's not all it's cracked up to be.

CNN and College

[pete-classic]

It's laudable that you are concerned about college, but you have the rest of your life to worry about job security. On the other hand the days in which you may bang 17-year-olds are numbered. Get your priorities straight.

-Peter

Jobs in the Free Market?

[reporter]

The free exchange of goods and services (including labor) between the United States and India damages how the (relatively) free market operates in the United States. The (relatively) non-free market in India has destroyed much of its economy. The majority of Indians are unemployed or underemployed. Although the news reports describing the tech boom in India is accurate, that boom is largely restricted to the tech sector. The remainder of the Indian economy is in terrible shape. Indian government intervention in that economy generates hordes of desperate labor that flood into the United States or into the Indian tech sector.

The final result is that, due to the free flow of services (including labor in the form of outsourcing) between the United States and India, Indian government intervention now indirectly damages the operation of the American free market (for high-tech labor), suppressing wages and diminishing working conditions.

You see a similar phenomenon in the unskilled-labor market. Mexican government intervention in the Mexican economy generates hordes of desperate labor that floods the American market for unskilled labor. The presence of Mexican illegal aliens in the American market suppresses wages and diminishes working conditions as American employers exploit a nearly limitless supply of desperate workers willing to work for slave wages in dangerous or grueling conditions.

No job in America is safe from this destruction to the free market.

You should select the job doing the kind of work that most interests you. In your spare time on the weekend, stay abreast of international news. Vote for populist politicians who support free trade between the United States and only other (relatively) free markets like Canada and Japan, not Mexico nor India. Support policies that terminate trade between the United States and (relatively) non-free markets like Mexico or India.

Also support policies that compel Washington to aggressively intervene in both the Mexican government and the Indian government. The nature of the intervention should be at least as aggressive as the Mexican meddling (by Vicente Fox and his corrupt ilk) in the American Congress. Washington should eliminate Mexican politicians and Indian politicians who promote the economic destruction that has generated hordes of desperate labor fleeing to the United States.

Re:Jobs in the Free Market?

[say]

No job in America is safe from this destruction to the free market.

This must be the least insightful comment on globalization I've ever seen. What constitutes a free market seems... vague. Do you really have any proof that government intervention in Canada is any less than in Mexico?

Here's a mind bending newsflash for you: The difference between the countries you want to trade with and the ones you don't want to trade with is that the non-tradables are _poor_, while the tradables are _rich_. You don't want free markets. You want protectionism, where the rich world is allowed to keep its benefits by keeping the poor away through immoral trade barrier.

So it isn't the free market that is being destroyed in the US, it is the protectionistic privileges. That's the true essence of the free market: it makes sure that cheapest (per quality unit) is preferred. And it's no way the US can remain cheapest without dropping some of its (relative) riches.

Re:Jobs in the Free Market?

[killjoe]

One important reason why developers can work for cheap in india is the prevelance of slave, indentured and child labor there. Because of a permanent underclass of slaves and near slaves the developers get all their needs for housing, food, clothing etc met dirt cheap. When your bricks are made by 14 year olds who have been sold into slavery it's pretty cheap to build a house.

If India ever outlaws child labor or the buying and selling of humans and gives the untouchables full rights the cost of development will go up there and the outsources will move to africa or use chinese prison laborers.

In actually a plummer gets just as much money as a code monkey if not more and your job is not likely to be outsourced. Think about it.

my advice to my kids and you

[iplayfast]

Do a job that you love. There are up sides and down sides to this but the up side is that you can enjoy going to work where you will spend a significant portion of you life. The downside is that your love may change and what used to be fun is now a chore. I was first a musician, and after 3 years on the road decided it was not fun anymore. I then went back to University and learned about computers. Luckily, I still love it 25 years later.

Another up side, is that if you love to do something you will get better at it. This means that you will become the craftsman that people want to have working for them. Your salary will increase and you will be employed.

A third upside is that your enthusiasm about your work will show. When you go for job interviews it will show. People feel more comfortable hiring someone who they can see has enthusiasm and a proven experience.

The nice thing about the computer field, is that it's large enough that you can partition your hobby and work into 2 different types of work, so you don't become overexposed in the one at work.

Re:Starting Salaries

[Brandybuck]

The starting salary only applies for those graduates who get jobs in the first place.

Having recently interviewed several candidates on campus, I'm starting to see why they're not getting hired. Most are unmotivated, but a lack of income will soon fix that. The real problem is that they don't have any real world skills. A university CS/CE graduate should either have enough hand-on programming experience to know which end of a compiler goes up, or enough theoretical knowledge to know the difference between the basic data structures. I'm not getting that from the candidates I'm interviewing.

Unless the universities straighten up, I think the future of university graduates is an extra year at DeVry/ITT just to get the skills to be employable.

Do what you love

[ggambett]

Do what you love. Be the best. The rest just happens.

Re:Starting Salaries

[jcr]

A university CS/CE graduate should either have enough hand-on programming experience to know which end of a compiler goes up, or enough theoretical knowledge to know the difference between the basic data structures. I'm not getting that from the candidates I'm interviewing.

I find that the quality of applicants varies enormously, even from the same school. I do see rather a lot of "grade inflation", but new CSEE graduates who had a 3.0 or better GPA are usually at least trainable.

What I try to seek out is whether a newly-minted CS degree holder likes the field, or just got steered to it by a guidance counselor. If the interest is there, the talent can generally be trained in.

-jcr

The first questions to ask yourself...

[chicago_scott]

I suppose the first questions to ask yourself is why you are looking at going into IT. Are you looking for a stable career? Are you looking for fortune? Do you really enjoy computers and programming as a hobby and think it would be cool to earn a living doing something you enjoy or are you just looking for any job that you can earn a living doing?

I went into technology as a programmer/software enginner because I loved working with computers and I saw a way make a living while doing something I love. Ten years later I still love it. I've always prefered hands on development and prefer coding and on some project I like being the technical lead, but otherwise I have avoided the management-side of IT. I could make more money, but at a huge cost to my personal satisifaction.

Why do you want to go into IT?

The Real World

[billybob_jcv]

I'm an IT director at a corporation with an IT staff of ~20 people. Our IT budget is fairly small - we typically have funds for 1-3 decent sized projects per year. But, like most companies our size, we do not have the full-time staff to continue maintenance on our existing systems AND run a dedicated project team to implement a new system. We bring in an implementation partner to staff the new projects - and members of our full-time staff generally act as the project manager and as part-time technical members of the team. The dedicated project team is primarily contractors. I worked for a while as a contractor when I was younger - and as many here can testify, it is not an easy life, and not for everyone. Traveling from customer to customer all over the country, staying in one place for only a few months at a time - and always having the threat of lay-off over your head if you don't find a spot on the next project. What's the problem? There are many. The full-time staff doesn't really get involved enough in the new system implementation - they are too busy with maintenance. Tight budgets make us push the schedules too hard - because we want the high-priced contractors gone as soon as possible. The contractors aren't in-house long enough to really refine the solution to match our business processes - they try to slam it in, get paid and move on - leaving us to clean-up the messes and deal with business users who are disappointed with 80% solutions. The real-world of corporate IT is an ugly place - full of long hours & weekends, clueless corporate execs and $500K software packages that won't even install unless you spend a thousand manhours patching and tweaking code. Schools don't teach this stuff - they show you a few theories for building data models and writing compilers and send you on your way. I'm not saying a degree is worthless - on the contrary, the discipline required to complete a university program is extremely valuable and I won't hire non-degreed script kiddies. It's just that IMO the university curriculum is completely unrelated to the world of corporate IT. One of my university professors told me something that has stuck with me for 20 years: Technical people are complete idiots. We believe we have a Holy Calling to be techies, and we like being techies so much that we would do the work even if we didn't get paid. Lawyers and accountants get paid so much because they charge you just to have a talk with them. If techies did the same thing we would all be making millions of dollars!