Technical Insight Quotes

I'm not a scientist. What I find interesting about my work is how, as a designer, I sit between science and the consumer and can see both a need and a solution.

The psychological profiling [of a programmer] is mostly the ability to shift levels of abstraction, from low level to high level. To see something in the small and to see something in the large.

We need business leaders who have a respect for technical issues even if they don't have technical backgrounds. In a lot of U.S. industries, including cars and even computers, many managers don't think of technology as a core competency, and this attitude leads them to farm out technical issues.

Reports in Washington show that our reasoning was just like that of your physicists. With all this information available, at least to privileged persons, I cannot understand why it is generally held in the United States that we completely missed the basic principle of the bomb until after Hiroshima.

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.

Just about every error has a technical and psychological component: get good at discovering those connections

The experienced physician, mechanic, or physiologist looking at a wound, an engine, a microscopic preparation, "sees" things the novice does not see. If both, experts and laymen, were asked to make exact copies of what they see, their drawings would be quite different.

If one has really technically penetrated a subject, things that previously seemed in complete contrast, might be purely mathematical transformations of each other.

Translation makes me look at how a poem is put together in a different way, without the personal investment of the poem I'm writing myself, but equally closely technically.