Programmers: Stop Calling Yourselves Engineers
theatlantic.com
Programmers: Stop Calling Yourselves Engineers
1–10 of 27 posts
Re: Programmers: Stop Calling Yourselves Engineers
#2No.
Re: Programmers: Stop Calling Yourselves Engineers
#3The author seems to have a naive view of what engineering is actually like:-)
There is a debate about certification but its not one that some one not working as an "engineer" - has much to say.
Re: Programmers: Stop Calling Yourselves Engineers
#4> It undermines a long tradition of designing and building infrastructure in the public interest.
How ridiculous that this is the introductory sentence. I guess leave it to the Atlantic to assume there are no engineers working for private enterprise.
Re: Programmers: Stop Calling Yourselves Engineers
#5I'll stop calling myself an Engineer when The Atlantic stops calling themselves news or journalism.
Re: Programmers: Stop Calling Yourselves Engineers
#6Author never heard of Electrical Engineers? I have graduated at Faculty of Electrical Engineering, the Computer Science department, and got a title of a Master of Electrical Engineering. Pretty sure I can call myself an engineer...
Re: Programmers: Stop Calling Yourselves Engineers
#7Oh man, can cannot emphasize enough how much i don't care about this.
"The traditional disciplines of engineering—civil, mechanical, aerospace, chemical, electrical, environmental—are civic professions as much as technical ones. Engineers orchestrate the erection of bridges and buildings; they design vehicles and heavy machinery;"
so what? Traditions change, names change, everything changes, software engineers will be called engineers and no one cares if they build bridges or not. I can tell you if i connect a xmpp service to some twitter account i also built a bridge. so software engineers do build bridges! And talking about "tradition" in a digital revolution is also weird, because right now everything is changing and nothing will be like before. This wolrd will never be the same as 1960, so why stick to old naming convetions anyway. This article is nothing but time-wasting, sorry if i offend someone with that but it is my honest opinion.
Re: Programmers: Stop Calling Yourselves Engineers
#8What's the difference between a programmer, developer, and a software engineer?
Re: Programmers: Stop Calling Yourselves Engineers
#9Re: Programmers: Stop Calling Yourselves Engineers
#10So many words written protesting a natural evolution of language.
Engineer started as a word meaning one who is skilled in the design, construction, or use of, surprise, engines.
The word evolved in its use to later encompass other systems that can build: civil engineering (bridges and buildings), mechanical engineering (robots and mechanical systems), and computer engineering (actual hardware).
Software is merely the latest system. Many universities grant software engineering degrees and apply principles of engineering to software.
The whole point of this article is to treat "engineering" as a reserved and hallowed word and vocation. Its name and usage must be protected at all costs lest we let just anyone call themselves an engineer.
It's an argument of arrogance and appeals to maintaining the status quo of exclusionary system. You didn't take a certain test or wear an iron ring? Sorry, you can't call yourself this one title. The title of "doctor" has similar historical exclusion, with infighting common amongst multiple professions (e.g., medical doctors not thinking dentists or PhD's are actual doctors).
Language evolves. Stop being protectionist about a certain word.