Quotes About Software

Because the software-creation process is out of control, the high-tech industry must bring its process to heel, or else it will continue to put the blame on ordinary users while ever-bigger machines sit dead in the water.

Software experts are—of necessity—comfortable with high-cognitive-friction interaction. They pride themselves on their ability to work in spite of its adversity. Normal humans, who are the new users of these products, lack the expertise to judge whether this cognitive friction is avoidable.

Change is impossible until senior business executives realize that software problems are not technical issues, but are significant business issues.

In all other construction disciplines, engineers plan a construction strategy that craftsmen execute. Engineers don't build bridges; ironworkers do. Only in software is the engineer tasked with actually building the product. Only in software is the ironworker tasked with determining how the product will be constructed. Only in software are these two tasks performed concurrently instead of sequentially. But companies that build software seem totally unaware of the anomaly.

I do not blame programmers for hard-to-use software, and I'm very sorry to have given any programmer a contrary impression. With few exceptions, the programmers I know are diligent and conscientious in their desire to please end users and are unceasing in their efforts to improve their programs' quality. Just like users, programmers are simply another victim of a flawed process that leaves them too little time, too many conflicting orders, and utterly insufficient guidance.

The intractability of the software-construction process—particularly the high cost of programming and the low quality of interaction—is simply not a technical problem. It is the result of business practices imposed on a discipline—software programming—for which they are obsolete.

We can create powerful and pleasurable software-based products by the simple expedient of designing our computer-based products before we build them.

When the creators of software-based products examine their handiwork, they overlook how bad it is. Instead, they see its awesome power and flexibility. They see how rich the product is in features and functions. They ignore how excruciatingly difficult it is to use, how many mind-numbing hours it takes to learn, or how it diminishes and degrades the people

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.

The language we use can subtly influence our thinking. […] On the face of it, the term "web platform" seems harmless. Describing the web as a platform puts it on par with other software environments. Flash was a platform. Android is a platform. iOS is a platform. But the web is not a platform. The whole point of the web is that it is cross?platform.

I have several computer companies. One of them I have a program for wide-format printing. I have a beauty program. So I have several different programs that I own for printing.

One man's crappy software is another man's full time job.

The first business plan is there to make sure you can use Microsoft Word.

Using a well-worn metaphor, culture can be viewed as the software that runs the hardware of human society.

Fiddling with a program until it appears to work is a reliable way of obtaining a program that almost works

Hardware had to be researched, purchased, secured, integrated, tracked, and disposed of. Software had to be licensed, configured, patched, updated, and eventually replaced. Networks had to be built, secured, upgraded, and inevitably rebuilt. And every component interacted with every other component in curious and unexpected ways, with unexpected occasionally culminating in catastrophic. The

Most software engineers are driven by pride of workmanship: we want to deliver products that we can stand behind, and that satisfy our users' needs.

VersionOne is a company that builds agile software tools, and also contributes to the agile community in many other ways.

Code is there to explain the comments to the computer.

We believe that the major benefits of testing happen when you think about and write the tests, not when you run them.

Coupled code is hard to change: alterations in one place can have secondary effects elsewhere in the code, and often in hard-to-find places that only come to light a month later in production.

There's a strong distinction to be made between dry code smart contacts and wet code's physical law. So law is based on our minds, our wetware - it's based on analogy. The law is more flexible; software is more rigid. Various laws tend to be batched in jurisdictional silos. Software tends to be independent.

Whatever you are studying right now, if you are not getting up to speed on deep learning, neural networks, etc., you lose. We are going through the process where software will automate software, automation will automate automation.

Oracle's latest database, version 12c, was specifically designed for the cloud. Oracle 12c makes all your Oracle applications multitenant applications without you having to make any changes whatsoever to your applications.