News for hackers. Stuff that matters.
Re:Do call yourself a programmer, and other career advice (2... by Alupis on Saturday February 07, 2015 @05:43PM (#9015583)
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.

Re:Do call yourself a programmer, and other career advice (2... by diminoten on Saturday February 07, 2015 @06:14PM (#9015675)
None 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.

Re:Do call yourself a programmer, and other career advice (2... by brudgers on Saturday February 07, 2015 @06:27PM (#9015733)
Just to clarify, in the US a PE (Professional Engineer) is not certified: Professional Engineers are licensed at the State Level to practice independently. Licensure comes with direct personal liability that cannot be assigned to a corporate person and a legal obligation to protect the public even if doing so is contrary to a client's wish or interest.

There's no equivalent in software, and the term "software engineer" has little of the rigor envisioned when Margaret Hamilton coined it.

Re:Do call yourself a programmer, and other career advice (2... by lifeisstillgood on Saturday February 07, 2015 @07:02PM (#9015854)
That is interesting - the idea of direct personal responsibility for flaws or bugs is one which would soon make NASA's development processes look lacksidaisical.

I do wonder how we will manage to actually become a profession.

Re:Do call yourself a programmer, and other career advice (2... by brudgers on Saturday February 07, 2015 @10:09PM (#9016278)
The idea of direct personal responsibility goes back 3500 years in construction. Basically people have to die from errors.
Re:Do call yourself a programmer, and other career advice (2... by lfuller on Saturday February 07, 2015 @06:29PM (#9015749)
In Canada it's illegal to call yourself an engineer without being licensed by the CCPE.
Re:Do call yourself a programmer, and other career advice (2... by TheCoelacanth on Sunday February 08, 2015 @01:44PM (#9018059)
And for the other 99.5% of the people in the world, different laws apply.
Re:Do call yourself a programmer, and other career advice (2... by icebraining on Saturday February 07, 2015 @06:22PM (#9015707)
In the US. Some other countries do have certification for software engineering.
Re:Do call yourself a programmer, and other career advice (2... by rational-future on Saturday February 07, 2015 @06:29PM (#9015744)
Which countries?
Re:Do call yourself a programmer, and other career advice (2... by icebraining on Saturday February 07, 2015 @06:56PM (#9015837)
Portugal, for example. You must be accredited by the official licensing body[1].

You can still be a developer, of course, and be responsible for critical software projects. You just can't call yourself an engineer.

[1] http://en.wikipedia.org/wiki/Ordem_dos_Engenheiros

Re:Do call yourself a programmer, and other career advice (2... by dylandempsey on Saturday February 07, 2015 @06:38PM (#9015779)
Canada
Re:Do call yourself a programmer, and other career advice (2... by eigenvector on Saturday February 07, 2015 @06:57PM (#9015840)
It 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

Re:Do call yourself a programmer, and other career advice (2... by dylandempsey on Saturday February 07, 2015 @07:19PM (#9015898)
It is actually a specific degree that is a minimum four years at specific Universities and then at least one year under another acknowledged Professional Engineer. You are then honoured with an Iron Ring that is well known in Canada that you can only obtain through the proper certification (as some colleges try to offer lesser degrees that aren't acknowledged). It's no different than a doctor or dentist, you can't legally professionally practice without it. The courses are geared towards theory, business, management and ethics rather than just proper or efficient coding and documentation.
Re:Do call yourself a programmer, and other career advice (2... by eigenvector on Saturday February 07, 2015 @07:41PM (#9015956)
The Iron Ring has nothing to do with the licensure of professional engineering. It is administered by the Corporation of the Seven Wardens which is not connected to Engineers Canada or any of the provincial or territorial licensing bodies.

Source: I have an iron ring.

Re:Do call yourself a programmer, and other career advice (2... by dylandempsey on Sunday February 08, 2015 @02:06AM (#9016634)
The point is, even socially it's weird here to claim you're an engineer if you don't have it
Re:Do call yourself a programmer, and other career advice (2... by ChainsawSurgery on Saturday February 07, 2015 @06:43PM (#9015799)
> But software engineering doesn't have that.

I actually wonder if (and subsequently when) software will move in that direction, though.

As computers become more and more involved in systems where loss of life is extremely possible (e.g. driverless cars), I wonder if there will be a big push to have PE-equivalents sign off on software architectures, etc.

I especially wonder if there will be a big push to do this in the near future simply for liability reasons ("well Jane Smith is the PE we contracted with and she signed off on the software architecture that didn't account for rain, so go sue HER.").

Not that computer errors haven't already cost lives to-date, but as software starts truly running everything we'll likely see a lot of grumbling and response to software errors that cost lives.

OTOH, it's worked pretty well without licensing to-date, so perhaps not. I do think regardless we'll see a more evident bifurcation into "developers" (most of us) and "software engineers" (people who work on mission-critical software) in the upcoming decades.

Re:Do call yourself a programmer, and other career advice (2... by themodelplumber on Saturday February 07, 2015 @06:05PM (#9015652)
Thanks for the list. Looks like I'm just a "documentation" away from becoming a sanitary engineer on my lunch breaks!
Re:Do call yourself a programmer, and other career advice (2... by p8952 on Saturday February 07, 2015 @05:58PM (#9015632)
The 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.

Re:Do call yourself a programmer, and other career advice (2... by logicallee on Saturday February 07, 2015 @07:06PM (#9015864)
Based on that list, you would do well as a 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
Re:Do call yourself a programmer, and other career advice (2... by hiou on Saturday February 07, 2015 @06:26PM (#9015728)
Let 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.

Re:Do call yourself a programmer, and other career advice (2... by walshemj on Saturday February 07, 2015 @08:02PM (#9016020)
as 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"
Re:Do call yourself a programmer, and other career advice (2... by analog31 on Saturday February 07, 2015 @06:48PM (#9015814)
Truth 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.
Re:Do call yourself a programmer, and other career advice (2... by austinz on Saturday February 07, 2015 @05:55PM (#9015626)
> 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?

Re:Do call yourself a programmer, and other career advice (2... by Alupis on Saturday February 07, 2015 @05:59PM (#9015635)
> 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.

Re:Do call yourself a programmer, and other career advice (2... by austinz on Saturday February 07, 2015 @06:24PM (#9015720)
Of course. Understanding the underlying principles is necessary but not sufficient wrt the practice of engineering.
Re:Do call yourself a programmer, and other career advice (2... by jaredsohn on Saturday February 07, 2015 @06:57PM (#9015841)
A "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.)
Re:Do call yourself a programmer, and other career advice (2... by rational-future on Saturday February 07, 2015 @06:27PM (#9015734)
Such 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.

Re:Do call yourself a programmer, and other career advice (2... by dang on Saturday February 07, 2015 @07:21PM (#9015911)
> 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

Re:Do call yourself a programmer, and other career advice (2... by kevin_thibedeau on Saturday February 07, 2015 @05:48PM (#9015602)
I feel for you. Too bad you've just violated the HN groupthink and will get downvoted for speaking the truth.
Re:Do call yourself a programmer, and other career advice (2... by andywood on Saturday February 07, 2015 @05:53PM (#9015618)
It'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.
Re:Do call yourself a programmer, and other career advice (2... by enraged_camel on Saturday February 07, 2015 @06:34PM (#9015767)
The older I get, the more I realize that "truth" is often a matter of perspective.