Slashdot Mirror
Software Engineers Ranked Best Job in America
fistfullast33l writes "CNNMoney and Salary.com have ranked the title of Software Engineer the best job in America. Computer IT Analyst also ranks 7th on the list, placing both technology positions in the top 10. From the article: "Designing, developing and testing computer programs requires some pretty advanced math skills and creative problem-solving ability. If you've got them, though, you can work and live where you want: Telecommuting is quickly becoming widespread.""
This story said that IT managers have the U.K's third-worst job -- ranking just below phone sex operator (No. 1) and ferry cabin cleaner (No. 2).
IT manager and software engineer are completely different jobs. That's like saying that an orderly and a trauma doctor have the same job.
"Well kids, you tried your best, and you failed. The lesson is, never try."
I've been both a software engineer and a system administrator/engineer. They both have their perks.
Software engineering I think gives you more of a sense that you're working on something really big, and there's obviously a huge sense of accomplishment when something you spent a year writing is used by thousands of people. On the flip side, though, you have to work for a year or more pounding away at code, with no real sense of accomplishment other than passing milestones. Often times, even that gives you no real sense of a job well done, since time frames for milestones are often set unrealistically, so you end up feeling lousy about missing a milestone instead of good for hitting one.
Then, there's the problem of usage. I've been a part of failed projects, and it can be gut wrenching. I've worked on applications that took 2 and 3 years to write, and ended up failing for various reasons. It sucks pouring so many hours into something and making all the sacrifices necessary to work 80 hour weeks just to have the project fail.
Being an SA, on the other hand, has its own rewards and issues. First, most SAs (unless you're a junior grade) don't babysit servers all day long, they generally are working on various projects to build or improve systems. These projects tend to be of a shorter duration than software projects, so there is generally more of an immediate sense of accomplishment. Also, you tend to be closer to the user base, which means you can easily see people using something you built on a day to day basis and draw some sense of accomplishment from that.
On the other hand, SAs also tend to be overworked, and can easily get caught up just trying to put out fires to maintain the servers rather than working on new and better things. A good SA will be able to stabilize things, but depending on the issue at hand that could take days or weeks or even months of very long hours before things return to where they should be. While a good SA will automate virtually every day to day task they can, sometimes they are too busy putting out fires to do so. This sort of thing can cause rapid burnout.
I spent 5 year being an SA, then spent 5 years being a software engineer, and now I'm back to being an SA again. Chances are good I will eventually be a software engineer again at some point. Both jobs have their advantages, and depending on where you work, both jobs can generate basically the same salaries.
So what exactly constitutes a "software engineer"?
# Debate_over_who_is_a_software_engineer
The question for the ages. Nobody really knows, to be honest. More accurately, we can't decide. Wikipedia touches on the subject, if you want to read more:
http://en.wikipedia.org/wiki/Software_engineering
"Times have not become more violent. They have just become more televised."
-Marilyn Manson
I understand what you are saying and think there are different perceptions about the terms. I too majored in CS but consider myself a software engineer. We started with 300, only 26 graduated (1990); 26 hours of math required.
Perceptions (right or wrong):
Software Engineer: plans, manages, and develops full end-to-end software work products. They work in industry where the phrase return-on-investment (ROI) is used daily, their organizations often answer to stock holders, and their reputation hinges on each successful effort.
Computer Scientist: conducts research, often in government / educational / research facilities where the terms Grant and Research Funding are more often used and they can often obtain tenure (a secure position).
Cogito Ergo Sum
The degree must be from an ABET certified school.
It strikes me as rather odd that the software engineer's "Ease of Entry" (open to everyone from high school drop-outs and up) is rated the same as a professor (minimum PhD for university, usually Master's for community college).
Software engineering is the planning, the requirements management, the development life cycle, and testing/fixing/maintaining that comes with each project.
Programming is just a small aspect, and most software engineers do programming as well as outlining the problems correctly.
Of course, if you've heard of a fishbone diagram, or work with UML or similar, then you might just be a software engineer.