This is a straw man. Requirements are the "what". Design is the "how". If I was handed a complete design, of course a compiler could translate that into a program a computer could understand. But, translating requirements into an appopriate design is the job of the programmer, at least in my experience. The actual typing is a side effect of the job.
in reply to Re^3: We are the logisticians of information
in thread Programming is combat
I look at it as an artform. Some people work in paint or food. I work in programming languages. The requirements could be "I want a picture of the Pieta." The design is the artistic layout - "The Virgin is on the left, the Christ-child on the right." The compiler is "Sculpt it in marble" or "Sculpt it in papaya". :-)
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested