When I was at Tek, I was frustrated that computer hardware was being improved faster than computer software. I wanted to invent some software that was completely different, that would grow and change as it was used. That's how wiki came about.
I took this 'how to build computers' course basically because I'm sick and tired of getting ripped off by cheesy computer companies. Software baffles me. I like hardware. I used to change my own oil, and now I want to build my own computer so I can have what I want.
My dad grew up as a computer programmer, so he always had random computer software, and I started opening up editing software at age 12 and figuring out how to build websites.
The most amazing achievement of the computer software industry is its continuing cancellation of the steady and staggering gains made by the computer hardware industry.
A smartphone is a computer - it's not built using a computer - the job it does is the job of being a computer. So, everything we say about computers, that the software you run should be free - you should insist on that - applies to smart phones just the same. And likewise to those tablets.
People usually compare the computer to the head of the human being. I would say that hardware is the bone of the head, the skull. The semiconductor is the brain within the head. The software is the wisdom. And data is the knowledge.
Software and hardware design is less different than software designers think, but more different than hardware designers think.
One would expect that a surge of new automation opportunities in highly paid work would catalyze a surge of corporate investment in computer hardware and software. Instead, the opposite occurred.
Even though most people won't be directly involved with programming, everyone is affected by computers, so an educated person should have a good understanding of how computer hardware, software, and networks operate.
The burgeoning field of computer science has shifted our view of the physical world from that of a collection of interacting material particles to one of a seething network of information. In this way of looking at nature, the laws of physics are a form of software, or algorithm, while the material world-the hardware-plays the role of a gigantic computer.
I am confident that we can do better than GUIs because the basic problem with them (and with the Linux and Unix interfaces) is that they ask a human being to do things that we know experimentally humans cannot do well. The question I asked myself is, given everything we know about how the human mind works, could we design a computer and computer software so that we can work with the least confusion and greatest efficiency?
Early on, when software was developed by computer scientists, just people working with computers, people passed around software because that was how you got computers to do things.
Software Engineering is that part of Computer Science which is too difficult for the Computer Scientist.
We shifted our philosophy from being a computer mapping group that would support planners to the idea of building actual software that would be well engineered. Because at that time, our software was not well-engineered at all; it was basically built with project funding and for project work, largely by ourselves.
Software is getting slower more rapidly than hardware becomes faster.
Similarly, computer literacy courses tend to produce computer people who know a lot about computers or a piece of software but they don't help people become fluent with the machine.
High-quality software is not expensive. High-quality software is faster and cheaper to build and maintain than low-quality software, from initial development all the way through total cost of ownership.