Ruptor wrote:Machine code was dead slow so assembler came along then Algol & Fortran driven by profits appeared and progress was lost to profit making where Pascal improved on Algol and the Americans came up with C for crap as their alternative and we were stuffed.
When I was at college, back in the 1980s (yes, I'm an old git!

) the talk back then was "a competent programmer will create, on average, 10 lines of debugged code, per day". So, given that 10 lines of debugged C or Pascal or Fortran or whatever contains a huge number of assembly level instructions, it's no wonder they wanted to get away from Assembler.
Machine code, back then - and I have done it - was setting up the mainframe (or whatever - for me, it was an old mainframe) switches on the front panel to get it to boot itself up. Tedious to say the least.
You seem a little against making profits? I wonder why? I don't think that higher level languages were developed for profit reasons, myself, I suggest they were invented to make things more efficient - those 10 lines of debugged code again! However, I would be interested in your sources.
Ruptor wrote:Why is there no interest in having computers do the coding? I know the design entry stage looks complicated to get it in to a form that a computer can code but once done software generation would explode and be available to everybody.

I write in high level languages, because it's easier than assembly language. I write in assembly because I like it and it's fun. But if I need to get something done, I do it in SuperBASIC, or C68 on the QL, C/C++ for the AVR microcontroller I play with, or BASH/C/C++ or PL/SQL at work, depending on what I need to do. If I write in assembler for any of that I'm either showing off (!) or I need the low level access and speed.
In the past I have written a lot of commercial code using a code generator. It was called Compuware from a company called Compuserve. It worked. It worked reasonably well in fact. But you have to work the the limits of that language, and to be honest, the only code it wrote was the database access parts - I still had to write the logic.
Filetab was another code generator. I built a truth table as my source code and it wrote the code to do what was needed. It too worked - but I was still writing some code to get it to do the needful.
I wrote a code generator to product SCL (System Control Language) scripts and Cobol programs for the ICL 29xx and 39xx series of mainframes back in the 1980s after college. They worked fine too - but the users still have to write the main code.
There was talk back in those days that soon programmers would be redundant as computers would eventually write all the code for everyone "at the touch of a button". Well, that never happened did it? Equally, Nuclear Fusion is just "10 years up the road" - they've been saying that for years too.
So, you want a computer to write code? Well, they are doing it now. You write in C or C++ and compile it - the compiler will write the Assembly language source for you. This is how it is, no matter what the code writer you need to create or use, someone will still have to write some sort of source code or program requirements description (and don't get me started of user's requirements - I had one once which simply said "write a program to produce invoices". I kid you not, that was it!) to input to the code generator to have it produce something that may or may not match up with what was requested or even, what was needed.
With no offence intended, you are living in a dream world if you think that computers will write code "just like that" any time soon, if at all ever. Software generation is pretty much already available to the masses - over 30 million Raspberry Pis have been sold, and counting. Python is installed and almost anyone can learn Python, I've even done some myself - and I'm still an old git!
Cheers,
Norm.