Hacker News new | ask | show | jobs
by jedberg 5970 days ago
Out of curiosity, what is your definition of a "real" engineer.

Or to put it another way, why isn't someone who writes software worthy of the title "Engineer"?

> Do people who work in software startups generally take Physics, Chemistry, Calc 1-4, Diff Eq, Statics, Dynamics and so on while at University?

That is kind of a broad question. But I can tell you that at Berkeley, everyone in the School of Engineering takes those classes, whether you are going to be a materials engineer or a software engineer.

Edit: I'll throw this out here too:

Definition of Engineering: The application of scientific and mathematical principles to practical ends such as the design, manufacture, and operation of efficient and economical structures, machines, processes, and systems.

I would posit that someone writing software uses scientific (debugging) and mathematical (algorithms) principles to practical ends.

1 comments

In many engineering disciplines you're legally forbidden from self-applying the title of "engineer" -- you have to be licensed and take formal legal responsibility for the quality of your work. That level of discipline and rigor is what most people are referring to when they distinguish between "software engineers" and "real" engineers.
It's not nearly that strict. You can't use the title "Professional Engineer" without licensing, but non-licensed engineers can and usually do use the term "engineer", or derivatives like "chemical engineer" on their business cards and resumes. It's the norm in firms with a lot of engineers (like, say, Exxon) that most of the people whose job title includes the word "engineer" are not PEs. It doesn't even really give you any benefit to be a PE in the corporate context, because everything you're doing is on behalf of the corporation anyway; you're not an independent contractor providing services that you have to legally stand behind, but an employee doing work for hire.

edit: This is true for the U.S. anyway. I believe some other countries are more strict on who may call themselves an engineer.

So would you be ok with calling people software engineers if they had to take a test to get a license and then be responsible for failures of their code in the future?
I'm not advocating a position either way. I'm explaining why people make the distinction.