Don't you hate it when a mechanical engineer tells you that computer programming is NOT engineering?

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Sukhoi

Elite Member
Dec 5, 1999
15,348
106
106
Computer science is not engineering. Engineering involves physical items. Computer code is not a physical item.
 

mugs

Lifer
Apr 29, 2003
48,920
46
91
Originally posted by: alphatarget1
You cannot build a program without knowing the engineering behind it. I can see programmers making an engineering application more user friendly, but all the math behind it is done by engineers.

Granted, but an engineer wouldn't have a clue how to program physics. It's not really as simple as just plugging in formulas.
 
Aug 16, 2001
22,505
4
81
Originally posted by: mugs
Originally posted by: spidey07
An engineer doesn't need to know how to build the tools, only use them.

Reference chimps making tools out of wood - they don't know how to use them. They just make them. The engineer chimp picks up said tool, gathers food with it and everybody happy.

He's not saying a web developer has to be able to build his tool (Dreamweaver), he's saying he should be capable of doing it without it. And he's saying a mechanical engineer should be able to design whatever he's designing without a CAD program.

Actually he can. It just takes much longer. A real Engineering program will teach you the methods to use when designing. The CAD tool is just a tool to make the process faster.
 

EmperorIQ

Platinum Member
Sep 30, 2003
2,003
0
0
Originally posted by: mugs
Originally posted by: shortylickens
The software is a tool for him to do real engineering.
Engineers have many tools.
Micrometers for example.

:thumbsup:

I'm a "software engineer" but I don't consider myself an engineer by any means.

are you just a code monkey then?
 

gopunk

Lifer
Jul 7, 2001
29,239
2
0
Originally posted by: alphatarget1
Originally posted by: gopunk
Originally posted by: alphatarget1
Originally posted by: gopunk
Originally posted by: LostWanderer
Sorry to dissappoint you, but a computer programmer or even some would be computer "engineers" haven't earned the title. Not to knock the fields, they're difficult and demanding in their own right, and certainly equal in stature in my view, but the term engineer should be rightfully reserved.

When you take 5-6 years of multidisciplinary engineering courses, sit for an 8-hour comprehensive everything you ever saw internship test, work for the man for 4 years, sit for another 8-hour comprehensive everything you know test that has < 50% passing rate, pass all that and become licensed, live with the daily threat of lawsuits for anything you sign your name to, while commiting yourself to putting the public welfare and safety above your own personal gain, then you've earned the right to call yourself an engineer.

<-- Licensed and practicing civil engineer.

by that standard, ChemE's, BioE's and EE's wouldn't even be engineers

I can see ChemEs having a lot of liability issues as well. I don't really know what BioEs do and EEs... they're a different species. :p

it's not hard to foresee software engineers encountering liability issues

If a ChemE fvcks up on something in a big chemical plant, crap blows up and things get polluted and stuff. I don't know enough about other fields besides civil/structural to comment on them so I'm basing my judgement on what I think they do.

Programmers can debug and stuff... You can't do that with a building, chemical plant, or car, period.

it's pretty rare that you'd be able to cover everything with tests... why is anything buggy at all? you can't catch them all. if a CE fvcks up, crap can blows u, and things can get polluted, etc as well. i don't know about buildings or chemical plants (i suspect there is a lot of modeling that is involved, which is analogous to testing software), but for cars and planes, they are tested out and the design is fixed/refined. what do you think wind tunnels are for?
 

vtqanh

Diamond Member
Jan 4, 2001
3,100
0
76
Originally posted by: her209
Originally posted by: shortylickens
The software is a tool for him to do real engineering.
Engineers have many tools.
Micrometers for example.
I guess what I'm trying to say is that if a "web developer" approached me and said I can make you a web page (using FrontPage/Dreamweaver/etc.) but couldn't write an functional HTML page by hand, I'd laugh in his face too.

:roll:
Using the same logic, I would probably laugh at you if you couldn't write an intepreter to interpret the HTML, the compiler that compile the language you're using to write the intepreter, ...so on...
There are different layers of abstraction and an engineer doesn't need to know them all.
 

EmperorIQ

Platinum Member
Sep 30, 2003
2,003
0
0
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.

Read on the Therac-25 incident.
 

alphatarget1

Diamond Member
Dec 9, 2001
5,710
0
76
Originally posted by: Mears
Originally posted by: alphatarget1
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

You have a ton of time to debug, testing and such.

You are obviously talking out of your ass.

My point still stands. How many times have you seen air/car accidents caused by computer problems? OK, a ECU can screw up and stop your engine I suppose. Airplanes, I don't recall that many getting into accidents because of software glitches.

On the other hand, Fatigue caused by cyclic loading isn't as easily detected and when the fuselage disintegrates, people die.
 

jinduy

Diamond Member
Jan 24, 2002
4,781
1
81
Originally posted by: mugs
Originally posted by: jinduy
Originally posted by: bharok
Originally posted by: mugs
Originally posted by: shortylickens
The software is a tool for him to do real engineering.
Engineers have many tools.
Micrometers for example.

:thumbsup:

I'm a "software engineer" but I don't consider myself an engineer by any means.

:thumbsup:

why's it called software engineer then?

http://en.wikipedia.org/wiki/Software_engineering

so i guess engineer is a fitting name?
 

her209

No Lifer
Oct 11, 2000
56,336
11
0
Originally posted by: alphatarget1
You cannot build a program without knowing the engineering behind it. I can see programmers making an engineering application more user friendly, but all the math behind it is done by engineers.
I don'd know if this is true with the other schools, but I had to take Math course up the ass. Mechanical Engineers stopped at around the Differential Eq stuff where the Comp Sci folks had to go way past that. Think of it this way. All it took to get a double major for the Comp Sci folks was only a couple more courses.
 
Aug 16, 2001
22,505
4
81
Originally posted by: alphatarget1
Originally posted by: gopunk
Originally posted by: LostWanderer
Sorry to dissappoint you, but a computer programmer or even some would be computer "engineers" haven't earned the title. Not to knock the fields, they're difficult and demanding in their own right, and certainly equal in stature in my view, but the term engineer should be rightfully reserved.

When you take 5-6 years of multidisciplinary engineering courses, sit for an 8-hour comprehensive everything you ever saw internship test, work for the man for 4 years, sit for another 8-hour comprehensive everything you know test that has < 50% passing rate, pass all that and become licensed, live with the daily threat of lawsuits for anything you sign your name to, while commiting yourself to putting the public welfare and safety above your own personal gain, then you've earned the right to call yourself an engineer.

<-- Licensed and practicing civil engineer.

by that standard, ChemE's, BioE's and EE's wouldn't even be engineers

I can see ChemEs having a lot of liability issues as well. I don't really know what BioEs do and EEs... they're a different species. :p

Liabilities for an EE? - There are many. Design something that won't go up in flames for example. Design stuff that has to work for 30 years without failing. Too much to list on a forum.
 

gopunk

Lifer
Jul 7, 2001
29,239
2
0
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

:thumbsup:

Guided missiles?

Again, you can test them in a controlled environment.

You can't do that with a building. You'll know whether an Engineer failed or not in a major event. Same goes for MEs, look at what happened to Challenger & Columbia.

Says the guy who apparantly isn't a software developer.

We've gone from "I don't see a programmer dude's failure will lead to fatalities" to "you can test them in a controlled environment." A "programmer dude's" mistakes CAN cause fatalities. You can't cover every real-world situation in testing. You think they didn't do extensive testing on the parts in the space shuttles? :confused:

My apologies, I don't know anything about software development.

I still believe that coding is something much more controllable than physical stuff.

if you don't know anything about it, you shouldn't be making statements about it

Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1

If a ChemE fvcks up on something in a big chemical plant, crap blows up and things get polluted and stuff. I don't know enough about other fields besides civil/structural to comment on them so I'm basing my judgement on what I think they do.

Programmers can debug and stuff... You can't do that with a building, chemical plant, or car, period.

Engineers can test their stuff - they test using MODELs. Often computer models. Who do you think programs those computer models? ... ... ... ? Better hope those code monkeys aren't just slapping stuff together. :roll:

You cannot build a program without knowing the engineering behind it. I can see programmers making an engineering application more user friendly, but all the math behind it is done by engineers.

i think the point is that because of the dependency on modeling, any liability other engineers are exposed to, software engineers are as well
 

EmperorIQ

Platinum Member
Sep 30, 2003
2,003
0
0
Originally posted by: Ready
programming is not engineering.
Writing scripts to for the sake of an engineering task is engineering.
I'm not a good programmer, but I write a few scripts to get the job done.

When I'm thinking about software engineering, I'm not thinking about scripts though. I don't think a web developer is qualified as a software engineer.
 

AccruedExpenditure

Diamond Member
May 12, 2001
6,960
7
81
Originally posted by: OdiN
Originally posted by: Alkesh
my roomate is a mech engineer. He's a cocky SOB who thinks he's the sh!t. He hates on social science majors because we have so much free time. I could have been an engineer if i wanted to, but i enjoy going out and having fun. he would always ask me to stay inside and drink with him at the apartment. This semester no go.

unsubscribe me

:thumbsup:
 

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

:thumbsup:

Guided missiles?

Again, you can test them in a controlled environment.

You can't do that with a building. You'll know whether an Engineer failed or not in a major event. Same goes for MEs, look at what happened to Challenger & Columbia.

Says the guy who apparently isn't a software developer.

We've gone from "I don't see a programmer dude's failure will lead to fatalities" to "you can test them in a controlled environment." A "programmer dude's" mistakes CAN cause fatalities. You can't cover every real-world situation in testing. You think they didn't do extensive testing on the parts in the space shuttles? :confused:

My apologies, I don't know anything about software development.

I still believe that coding is something much more controllable than physical stuff.
Actually, I'd say it's less controllable. When you build a building, no one expects it to be able to survive above & beyond conditions like a plane going in to it for example, and if this case does happen you're both given more time, money, and resources to make it happen. With computer programming, your application is simply expected to be bulletproof under all cases otherwise it's a failure, even though it could take years to debug even a moderate program, but you're almost never given the time/money to do such things. Physical engineering in turn is more controlled, IMHO.
 
Sep 29, 2004
18,656
68
91
Originally posted by: her209
And then he turns around and continues to work on his CAD model. :roll:

Ask him what he thinks of those "geeks" that know finite model analysis and know how to write software that does teh mathematics of complex models in highly optimized code. Ya, some of us jnow his job and ours.

Sometiems it's engineering. Software mostly relates to Architecture though, not engineering. Bottom line, you screw up and people can die. A ship can sink due to software or structural failure.
 

alphatarget1

Diamond Member
Dec 9, 2001
5,710
0
76
Originally posted by: gopunk
Originally posted by: alphatarget1
Originally posted by: gopunk
Originally posted by: alphatarget1
Originally posted by: gopunk
Originally posted by: LostWanderer
Sorry to dissappoint you, but a computer programmer or even some would be computer "engineers" haven't earned the title. Not to knock the fields, they're difficult and demanding in their own right, and certainly equal in stature in my view, but the term engineer should be rightfully reserved.

When you take 5-6 years of multidisciplinary engineering courses, sit for an 8-hour comprehensive everything you ever saw internship test, work for the man for 4 years, sit for another 8-hour comprehensive everything you know test that has < 50% passing rate, pass all that and become licensed, live with the daily threat of lawsuits for anything you sign your name to, while commiting yourself to putting the public welfare and safety above your own personal gain, then you've earned the right to call yourself an engineer.

<-- Licensed and practicing civil engineer.

by that standard, ChemE's, BioE's and EE's wouldn't even be engineers

I can see ChemEs having a lot of liability issues as well. I don't really know what BioEs do and EEs... they're a different species. :p

it's not hard to foresee software engineers encountering liability issues

If a ChemE fvcks up on something in a big chemical plant, crap blows up and things get polluted and stuff. I don't know enough about other fields besides civil/structural to comment on them so I'm basing my judgement on what I think they do.

Programmers can debug and stuff... You can't do that with a building, chemical plant, or car, period.

it's pretty rare that you'd be able to cover everything with tests... why is anything buggy at all? you can't catch them all. if a CE fvcks up, crap can blows u, and things can get polluted, etc as well. i don't know about buildings or chemical plants (i suspect there is a lot of modeling that is involved, which is analogous to testing software), but for cars and planes, they are tested out and the design is fixed/refined. what do you think wind tunnels are for?

Sorry I come across as arrogant on something I don't know about...

Buildings don't necessarily have to be modeled, most buildings follow either IBC, SBC, CBC and a couple of major building codes and they give you design values.

There is no way you will know how big of an earthquake or how fast the wind speed will be... Almost all buildings are built so that it can withstand, say, a 100 year quake (quake occurs every 100 years) and that's covered in building code. I don't know much about ChemE.

Wind tunnels can't test cyclic loading on an airfoil after 200 flights, I don't think it'll be cost effective, at least.
 

JinLien

Golden Member
Aug 24, 2005
1,038
0
0
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

:thumbsup:

Guided missiles?

Again, you can test them in a controlled environment.

You can't do that with a building. You'll know whether an Engineer failed or not in a major event. Same goes for MEs, look at what happened to Challenger & Columbia.

Says the guy who apparantly isn't a software developer.

We've gone from "I don't see a programmer dude's failure will lead to fatalities" to "you can test them in a controlled environment." A "programmer dude's" mistakes CAN cause fatalities. You can't cover every real-world situation in testing. You think they didn't do extensive testing on the parts in the space shuttles? :confused:

My apologies, I don't know anything about software development.

I still believe that coding is something much more controllable than physical stuff.
Does it matter whether or not programmers call themselves engineer or typist, or janitors call themselves sanitation engineer?

They are all human and are doing honest work and everyone should be treated with equal respect. It doesn?t mean that people with elitist titles such as king, emperor, shah, and president are better than the average people because they are not impervious to crimes, and there are great people that don?t hold any great title in this world that would sacrifice them selves to save others.

 

gopunk

Lifer
Jul 7, 2001
29,239
2
0
Originally posted by: alphatarget1
Originally posted by: Mears
Originally posted by: alphatarget1
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

You have a ton of time to debug, testing and such.

You are obviously talking out of your ass.

My point still stands. How many times have you seen air/car accidents caused by computer problems? OK, a ECU can screw up and stop your engine I suppose. Airplanes, I don't recall that many getting into accidents because of software glitches.

On the other hand, Fatigue caused by cyclic loading isn't as easily detected and when the fuselage disintegrates, people die.

http://www5.in.tum.de/~huckle/bugse.html

dunno if there are any car accidents, but there are accidents involving far more expensive equipment (mars climate orbiter, for one)
 

alphatarget1

Diamond Member
Dec 9, 2001
5,710
0
76
Originally posted by: her209
Originally posted by: alphatarget1
You cannot build a program without knowing the engineering behind it. I can see programmers making an engineering application more user friendly, but all the math behind it is done by engineers.
I don'd know if this is true with the other schools, but I had to take Math course up the ass. Mechanical Engineers stopped at around the Differential Eq stuff where the Comp Sci folks had to go way past that. Think of it this way. All it took to get a double major for the Comp Sci folks was only a couple more courses.

I don't see how you can write an ME program without knowing the ME behind what you're trying to model...
 

EmperorIQ

Platinum Member
Sep 30, 2003
2,003
0
0
Originally posted by: herm0016
im a mechanical engineer. . . dont hate me! wow. you guys are gettin real up tight about this. engineering is usually described as doing something physical. like finding a problem with a car and making a part to fix it. that is engineering in genral. anyone can "engineer". most computer and software engineering criculims that i have encounterd dont teach real engineering practices like statics and thermodynamics and meterial science, they teach you how to use a computer and how to build one. i belive that engineers need the background in the physical world that most computer degrees dont give you.

those are my thoughts. now you can rip them apart. . .

alright man, if you really take a look at what you wrote. You are basically describing your profession as engineering, and then saying: "dude, software engineers don't do that, so they aren't engineers." Really think about it man. Its like me saying "Dude, you don't have to spend hours coming up with algorithms to solve a problem, you have machines give you data, that's not real engineering work."

Another analogy would be you saying: "I'm human, and I can run a mile in 7 minutes, if you can't run a mile in 7 minutes you're not human."
 

alphatarget1

Diamond Member
Dec 9, 2001
5,710
0
76
Originally posted by: gopunk
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

:thumbsup:

Guided missiles?

Again, you can test them in a controlled environment.

You can't do that with a building. You'll know whether an Engineer failed or not in a major event. Same goes for MEs, look at what happened to Challenger & Columbia.

Says the guy who apparantly isn't a software developer.

We've gone from "I don't see a programmer dude's failure will lead to fatalities" to "you can test them in a controlled environment." A "programmer dude's" mistakes CAN cause fatalities. You can't cover every real-world situation in testing. You think they didn't do extensive testing on the parts in the space shuttles? :confused:

My apologies, I don't know anything about software development.

I still believe that coding is something much more controllable than physical stuff.

if you don't know anything about it, you shouldn't be making statements about it

Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1

If a ChemE fvcks up on something in a big chemical plant, crap blows up and things get polluted and stuff. I don't know enough about other fields besides civil/structural to comment on them so I'm basing my judgement on what I think they do.

Programmers can debug and stuff... You can't do that with a building, chemical plant, or car, period.

Engineers can test their stuff - they test using MODELs. Often computer models. Who do you think programs those computer models? ... ... ... ? Better hope those code monkeys aren't just slapping stuff together. :roll:

You cannot build a program without knowing the engineering behind it. I can see programmers making an engineering application more user friendly, but all the math behind it is done by engineers.

i think the point is that because of the dependency on modeling, any liability other engineers are exposed to, software engineers are as well

Yep, I apologized already for the comments made about coding.

You can't depend on the model all the time, a lot of it is experience and engineering judgement.
 

alphatarget1

Diamond Member
Dec 9, 2001
5,710
0
76
Originally posted by: JinLien
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: alphatarget1
Originally posted by: mugs
Originally posted by: her209
Originally posted by: alphatarget1
Computer science is not engineering in a traditional sense.

Stuff you do as a licensed professional engineer carry a lot of liability (human life, for instance). I don't see a programmer dude's failure will lead to fatalities.
Buggy software in an airplane/car/etc?

:thumbsup:

Guided missiles?

Again, you can test them in a controlled environment.

You can't do that with a building. You'll know whether an Engineer failed or not in a major event. Same goes for MEs, look at what happened to Challenger & Columbia.

Says the guy who apparantly isn't a software developer.

We've gone from "I don't see a programmer dude's failure will lead to fatalities" to "you can test them in a controlled environment." A "programmer dude's" mistakes CAN cause fatalities. You can't cover every real-world situation in testing. You think they didn't do extensive testing on the parts in the space shuttles? :confused:

My apologies, I don't know anything about software development.

I still believe that coding is something much more controllable than physical stuff.
Does it matter whether or not programmers call themselves engineer or typist, or janitors call themselves sanitation engineer?

They are all human and are doing honest work and everyone should be treated with equal respect. It doesn?t mean that people with elitist titles such as king, emperor, shah, and president are better than the average people because they are not impervious to crimes, and there are great people that don?t hold any great title in this world that would sacrifice them selves to save others.

I honestly don't really care for the title. I was trying to point out the stuff that traditional "engineers" do that software engineers don't do.