|
|
|
|
|
by ken
2435 days ago
|
|
And yet, even after seeing firsthand that computer programming is "extraordinarily similar" to the work of a vehicle mechanic, you still refer to it as "software engineering". Do we think it has anything in common with engineering? Why not call your work something like "software mechanic" or "software artisan"? What is with the continued need for programmers to try to aspire to engineering, while not actually being licensed engineers or practicing engineering? I don't think anyone outside the field takes programmers any more seriously when they call themselves "software engineers". Software overall is still late, slow, hard to use, buggy, and insecure. Nobody's fooling anyone. |
|
What I do as a developer is "design, build, and maintain" some software, and while it may not be physical, the use of the software is a physical activity. In this way, software has a physical existence at the very end of the process, same as a bridge or other object, though you just touch or fiddle with it through an intermediary physical object.
I'm not sure I see why someone would be upset about use of the term engineer, unless they are an engineer and somehow see developers as 'other' and it makes them angry that someone may be intruding into what they perceive as some private club.
Besides, I didn't decide to be called a "Software Engineer", that was a title bestowed upon me by a company. Before that I called myself a "programmer" and that's what I tell people I am. Now that I know "software engineer" might annoy someone and/or make me seem loftier / more worth taking seriously, perhaps I'll start calling myself an engineer.