|
|
|
|
|
by aeonsky
4459 days ago
|
|
While it might make one feel better to call oneself an engineer (you're not, it is not one of the original engineering practices), a developer (I guess, is it any better though), guru, ninja, evangelist (rebranded words). There is absolutely no need for these names in the software context. All of these words are made for the touchy-feely Gen-Y'ers (which I am a part of). While everyone tries to make the word "programmer" a dirty word these days, I'm proud to call myself one. When I go into job descriptions, I would put "Helped architech...", "developed a...", "designed flow of...", and etc. |
|
The American Engineers' Council for Professional Development (ECPD, the predecessor of ABET) has defined "engineering" as: The creative application of scientific principles to design or develop structures, machines, apparatus, or manufacturing processes, or works utilizing them singly or in combination; or to construct or operate the same with full cognizance of their design; or to forecast their behavior under specific operating conditions; all as respects an intended function, economics of operation or safety to life and property.
Software engineers take scientific methods created/researched/etc from Computer Scientists and created something from it. The difference between an engineer and joe shmo is that an engineer understands the science behind what they are doing.
An engineer could build a bridge and a regular guy could build a bridge. Both may work for 100 years, but the engineer KNOWS it will work for 100 years (under specific conditions obviously) and the regular guy doesn't. The same could be said for software.
https://en.wikipedia.org/wiki/Engineering