I have a degree in computer science (mainly software oriented, but included some hardware design), but people still say I am 'just a programmer'. Most programmers don't just 'do code', they do systems analysis, systems design, program development including some coding, testing at various levels, systems maintenance, and in there is a lot of 'interfacing' with suits and customers. Very little is coding. Of a properly done developed system lifecycle, less than 10% is normally coding.
There are the 'coder factories' that advertise on late night TV. The people that come out of there, and even out of high-school and Jr Colleges or trade schools are all dropped in the same pool as 'programmers'. Most programmers, at least the better ones, view their code as in many ways an art form. Once upon a time (think '70s) using 'tricks' to save memory was a big thing and was often used as some sick form of 'job security'. From what I have seen most individuals are over that, but not so much commercial software companies that think 'protectionism' is 'protecting their assets'. Much code has been 're-implemented' by doing blackbox reengineering.
There is still a place for the arts in computers and even software, but making things run better, faster, be smaller, use less resources, use 'vertical' AND 'horizontal' computer power, failsafe, encryption, API's, easier to network/interface, secure, better human interface, usability, etc.
Yes, I have studied the history of computing both academically and as a personal interest. That includes anything from mechanics of the babbage engine, digital systems design (that has been useful several times since school in 'doing what everyone says can't be done'), studying the architecture of the Saber System (hardware and software from IBM for American Airlines - now antiquated, but a leap forward in interactive computers, networking, and database architecture). I have worked with some of the architects and developers of the original National Semiconductor UART chips and the IBM HASP system originally written for NASA to keep them from being kicked out of NASA in Houston. Knowing HOW these worked, how the succeeded and failed ALL helped in my systems I wrote for customers (Mainly Fortune 500 types but includes medium to mom&pop shops).
It has been interesting studying some of the big failures and successes of the past, both in computing and business. Seeing the advanced systems before they were appreciated by the public. Seeing the marketing faux pas of large and small companies. For many small companies it is fatal, for large it hurts reputation even if they get through it (Ford Edsel, Apple Lisa, New Coke, we can all name some more).
I don't think EVERYONE needs to get as deep into it as I have, but it would help understanding and appreciation of the history both technical and of the people and times when developing solutions for today and the future.
Education is never lost. It just adds to the tapestry of life.
