My background is in hardware design. I found hardware work to be a welcome change from thousands of hours of programming and that led to the designs you mentioned.
Sentiment: POSITIVE
I was much more interested in making things than in designing them.
So I went for engineering, specifically product design, which I enjoyed.
I joined the staff of EMI in Middlesex in 1951, where I worked for a while on radar and guided weapons and later ran a small design laboratory. During this time, I became particularly interested in computers, which were then in their infancy. It was interesting, pioneering work at that time: drums and tape decks had to be designed from scratch.
I discovered at an early age that all I've ever wanted to do is design.
People who are more than casually interested in computers should have at least some idea of what the underlying hardware is like. Otherwise the programs they write will be pretty weird.
Architecture is changing faster than some other professions.
In designing hardware to be used every day, it was important to keep both the human aspects and the machine in mind. What looks good also often feels good.
I always considered programming as being like modern-day wizardry. You could think of things in your mind and then make them happen.
Look at what Silicon Valley has done - the advance of computers.
I'm not a programmer myself, but I am a very, very picky end user of technology. I like my machines to work they way they're supposed to, all the time.
No opposing quotes found.