5 ms·
You can only call yourself an Engineer under specific circumstances: 1) You follow a well defined and repeatable process 2) You are able to measure progress
by Alupis 12y ago
You can only call yourself an Engineer under specific circumstances:
1) You follow a well defined and repeatable process
2) You are able to measure progress
3) You have predictable results
4) You are capable of adapting to requirements change
5) You follow a standard of some sorts (coding style, organization, etc)
6) You provide thorough documentation
People who don't adhere to these principals are just developers/programmers. If you just set out and hack on some project, then you are not engineering something. A lot of engineers hack/develop/program on their free time, but as a professional on a professional project they adhere to these principals (and therefore are engineering).
There are a lot of people in this world who call themselves engineers without actually being an engineer. "Customer Service Engineer"... what are you actually engineering? In software in particular, there's a lot of people who just don this title because it sounds more impressive ("Systems Engineer" instead of just calling themselves an Admin)... but if you speak with them about their process, etc... it becomes clear they just hack on something until is works (sort of). That's not engineering; that's not a well defined and repeatable process that one can follow every time and produce predicable results. They aren't able to measure their progress other than a best-guess.
- kevin_thibedeau 12y agoI feel for you. Too bad you've just violated the HN groupthink and will get downvoted for speaking the truth.
- andywood 12y agoIt's not a matter of truth, just convention. "Software Engineer" is a title used in many organizations - not a subtype of engineer. It means programmer. Trying to apply arbitrary qualifications after the fact to make it more "engineer-like" is misguided. Some of us are called Architect even though we don't design buildings or use CAD software to design our products.
- enraged_camel 12y agoThe older I get, the more I realize that "truth" is often a matter of perspective.
- austinz 12y ago> but if you speak with them about their process, etc... it becomes clear they just hack on something until is works (sort of). Do you think these sort of people still try to possess the underlying mental model needed to know how the system works and what effects changing something will have on the system? Or are they literally cut-and-paste/change-something-till-it-works coders to whom the actual code is little more than meaningless incantations?
- Alupis 12y ago> Do you think these sort of people still try to possess the underlying mental model needed to know how the system works and what effects changing something will have on the system? I think that would depend on the individual -- but largely yes, I think they do. But that still isn't engineering. They haven't clearly and thoroughly documented the system so that anyone else can step in and replace them if need-be. They aren't capable of measuring their progress since it's going to be an unknown guestimation (which phase of the project are you in currently and how long until this phase is completed and we can move onto the next phase?). A massive requirements change might throw this type of individual off and lead to a mental wall since the new requirements don't fit into their mental model of the system. And most importantly, their process is not well defined nor repeatable to the extent they could follow the exact same steps on new projects and predicably produce results.
- austinz 12y agoOf course. Understanding the underlying principles is necessary but not sufficient wrt the practice of engineering.
- p8952 12y agoThe title of "Systems Engineer" generally refers to someone who designs and implements systems, as opposed to a "Systems Administrator" who administrates these systems. Are they a "true" engineer? That's probably not for me to say, but the roles of "Systems Engineer" and "Systems Administrator" are very different things in my experience.
- themodelplumber 12y agoThanks for the list. Looks like I'm just a "documentation" away from becoming a sanitary engineer on my lunch breaks!
- diminoten 12y agoNone of this is true. You can call yourself an engineer for any/no reason whatsoever. What you're getting at is some kind of industry certification, like the PE, that would only allow those who qualify to call themselves engineers. But software engineering doesn't have that. Therefore, anyone can call themselves an engineer if they want to, and don't have to pass your little criteria here.
- deleted 12y ago[deleted]
- icebraining 12y agoIn the US. Some other countries do have certification for software engineering.
- rational-future 12y agoWhich countries?
- dylandempsey 12y agoCanada
- eigenvector 12y agoIt is true that a person whose primary area of practice is software can become a professional engineer in all Canadian jurisdictions, but is comparatively difficult to meet the experience requirements relative to traditional engineering disciplines and very few software professionals hold a P.Eng. license even though they may have the relevant degree. The license is also seen as largely irrelevant in software as unlike traditional disciplines there are no legislative requirements to have a P.Eng. sign off on certain types of work, nor does most software development fall under the definition of engineering. In contrast, I work in the power industry and the involvement of a P.Eng. is usually a necessity at the design, construction and commissioning phases of utility electrical work. Also, Canadian jurisdictions do not distinguish between disciplines of engineering in licensing, a Professional Engineer is responsible for self-regulating themselves to the areas of practice in which they are competent. That is, a Professional Engineer holding a degree in mechanical engineering can seal electrical schematics, if she feels that she is competent to do so. In short, yes you can be a Professional Engineer as a software developer in Canada, but since most software work is not considered to be engineering under the official definition[1], one does not need to be a P.Eng. to do it. [1] http://peo.on.ca/index.php?ci_id=1813&la_id=1 http://peo.on.ca/index.php?ci_id=1813&la_id=1
- hiou 12y agoLet me just sit back and take in a big whiff of that smug. Ahhhhh.... Engineering is implementation. Nothing more nothing less. Sometimes it's messy and barely getting something done. Sometimes it's about dotting every i and crossing every t. A good engineer knows when each and how much of each is needed when implementing a solution.
- walshemj 12y agoas I remember it described as "an engineer is a scientist with thumbs - but if you want to really know how it works ask the technician"
- rational-future 12y agoSuch a stupid nonsense!!!! Spend a few hours reading about the industrial revolution and you'll see NONE of this applies to the greatest mechanical engineers in history.
- dang 12y ago> Such a stupid nonsense!!!! When disagreeing, please reply to the argument instead of calling names. E.g. "That is an idiotic thing to say; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- analog31 12y agoTruth be told, a lot of people with mainstream engineering titles (electrical, mechanical, etc.) don't actually engage in engineering according to your list. It's remarkably easy to be turned into a glorified CAD operator. A lot of product design work is tantamount to hacking -- mostly by trial and error.
- jaredsohn 12y agoA "Customer Service Engineer" is building/implementing a process where customers are able to interact with the company about the product they have paid / are paying for. Think of it as a SaaS where not everything can be automated (which is similar to creating a website to determine product/market fit that just includes a form which when filled out has you do the legwork related to your service manually.)
- logicallee 12y agoBased on that list, you would do well as a source-to-source compiler :) http://en.wikipedia.org/wiki/Source-to-source_compiler http://en.wikipedia.org/wiki/Source-to-source_compiler 1) You follow a well defined and repeatable process 2) You are able to measure progress 3) You have predictable results 4) You are capable of adapting to requirements change 5) You follow a standard of some sorts (coding style, organization, etc) 6) You provide thorough documentation