What the heck is the difference between a "computer programmer" and a "software engineer"

[deathbow2134]

The U.S. Bureau of Labor considers software engineers and programmers different things, while alot of people seem to think they are the same thing. The Bureau says "Computer programmers are at a much higher risk of having their jobs outsourced abroad than are workers involved in more complex and sophisticated information technology functions, such as software engineering." The Bureau also says that number of programming jobs is expected to slowly decreace while software engineering jobs will increace by over 20%. BUT ALOT OF PEOPLE USE THE TERMS INTERCHANGABLY!

They imply that software engineers decide how a program will be as a whole, and then pass down small insturctions down to the programmers. Software engineers make more money then programmers do, but they both usually have the same education (Bachelors degree in computer science)....what's up with that!?


Someone please enlighten me!

[Tony]

In the United States, where the term engineer is not regulated, people like to call themselves such, because it sounds cooler.

Strictly speaking, Computer Science is Math, Algorithms, computation, etc. Software Engineering is design of software systems. Both disciplines have a lot of overlap, and both disciplines heavily use programming as a tool to explore theories learned, in practice.

[matt271]

i would assume a computer programmer programs software and a software engineer [i[engineers[/i] software :]

no really i have no idea hagha

[SJ]

i'm taking a guess here. SE has more courses in how to design, produce, and maintain software. While CS is really, well, just CS. CS can lead into research and such, while SE doesnt really but it focuses on the software stuff. If CS wants to work where SE is working at, then they'd have to start lower. Like you said, SE is more likely to turn out product managers. but eventually a good CS grad can be a SE too.

[Tony]

And a good SE grad could be a CS too

[btiffin]

Software engineer; Bridge Designer, with knowledge of material tolerances and all the associated load calculations.

Computer Programmer; Bridge Builder, perhaps a crane operator, perhaps a mucker who does the necessary digging of mud and pouring of concrete.

Nothing stops a bridge designer from picking up a shovel once in a while.

Nothing stops a mucker from reading books and learning the on and offs of physics, materials and engineering. But luckily for us, as Tony pointed out, they don't get the iron ring until they can prove they know how to design a bridge.

Cheers