Message: 6
Date: Tue, 5 May 2020 19:50:48 +0000
From: "McMillan, William W" <william.mcmillan@cuaa.edu>
To: "members@sigcis.org" <members@sigcis.org>
Subject: Re: [SIGCIS-Members] Programmer vs. coder vs. sofware
developer vs. software engineer
Message-ID:
<BCD19775A5154645AD4E79C257C1E37A02812E64F6@CUAA-EX02.cuaa.cuw.edu>
Content-Type: text/plain; charset="us-ascii"
Thanks to those who sent suggestions for background info on this topic!
My own interest in the history of computing is really more about understanding the present, and my concern about the use and misuse of professional titles, though informed by history, leads to questions such as:
- Why do we call programmers and software developers coders nowadays, when that term has long been used to label those with quite limited intellectual involvement in software development, and even considered to be carrying out a clerical task (as explained
well in Nathan's book)?
- Why do we apply the term software engineer to those who can program, but who really know very little about software engineering in the broader sense?
To me this suggests that our society, and the enterprises that create the software we use, have extremely limited understanding of software development and what it entails. This is a failure of those of us who teach computing and software engineering and maybe
of professional societies.
The risks to society are immense. Imagine if a machinist or even a self-taught tinkerer could adopt the title mechanical engineer at will and be tasked with designing the critical devices of our civilization. Or if anyone with some knowledge of biochemistry
could serve as a pharmacist?
Maybe SIGCIS members don't believe that this topic belongs on this list, but I feel that historians might be better positioned to address it than many in the technical and commercial communities who are consumed by immediate demands, and who have very limited
understanding of their profession's past.
OK, end of rant!
Thanks,
Bill