Quotes About Interfaces

A long time ago, we had to build interfaces to connect with other companies, and I thought that was a great idea. The company had to pay a lot of money to build it and basically launched it, but our whole operating system almost broke. So, we couldn't continue it. In the end, I had to go on the train to Paris to explain that I had spent millions.

Given all the problems associated with Cloneable, new interfaces should not extend it, and new extendable classes should not implement it.

One lesson we learned the hard way after years of NetBeans API development is, "Don't put setter methods in the true API." By "true API," we mean the interfaces that must be implemented to provide something. If setter methods are needed at all—and usually they aren't—they belong only in the convenience base classes.

I'm interested in ways that digital interfaces can be utilized as powerful narrative devices, and to engage people in new and exciting ways.

The Ethereum client is literally a fork of Chromium's webkit backend. The idea is that users can build their own interfaces with HTML/JavaScript just like websites, and they will be viewable with the browser much like websites are viewable with the web browser.

Facilitate and document business analysis. Assist the project manager in defining project scope. Estimate needed time and resources. Define and design interfaces to external applications.

On the other hand, a system being developed by five different teams, each of which includes seven developers, cannot make progress unless the system is divided into well-defined components with reliably stable interfaces. If no other factors are considered, the architecture of that system will likely evolve into five components—one for each team.

Don't refer to volatile concrete classes. Refer to abstract interfaces instead. This rule applies in all languages, whether statically or dynamically typed. It also puts severe constraints on the creation of objects and generally enforces the use of Abstract Factories.

ISP: The Interface Segregation Principle This principle advises software designers to avoid depending on things that they don't use.

As our various electronic devices gain more and more sensory awareness, we open up the potential for entirely new forms of interaction. Not just new interfaces - tapping and shaking and whatnot - but a shift in presence.

An ugly system is one in which there are special interfaces for everything you want to do. Unix is the opposite. It gives you the building blocks that are sufficient for doing everything. That's what having a clean design is all about.

The fact that we are still sitting on and depending on technical protocols nearly a half century old is a testament to the genius of those who invented everything from such inventions, protocols and standards like Ethernet to personal computers that were more than just circuit boards for geeks, but actually had small GUI interfaces, as well as connected devices such as a mouse and keyboard.

A computer is a general-purpose machine with which we engage to do some of our deepest thinking and analyzing. This tool brings with it assumptions about structuredness, about defined interfaces being better. Computers abhor error.

First, I'd like to see the basic tools such as compilers, debuggers, profilers, database interfaces, GUI builders, CAD tools, and so forth fully support the ISO standard.

Innovators are developing the ideas and bringing them to life in amazing new applications. All we, as an industry, need to do now is focus on standardizing the interfaces to ensure interoperability - and stand out of the way.

As devices continue to shrink and voice recognition and other kinds of alternative user-interfaces become more practical, it is going to change how we interact with computing devices. They may fade into the background and just be around, allowing us to talk to them just as we would some other trusted companion.

Versioned interfaces are a reasonable compromise when you absolutely must introduce new operations to an existing interface-based abstraction without affecting client code. They are not a long-term solution for frequently changing abstraction, because of the complexity they create both for client and framework developers.

Folk wisdom in software development teaches that interfaces shouldn't be unduly influenced by implementations. Writing a test first is a concrete way to achieve this separation.

When pragmatists buy, they care about the company they are buying from, the quality of the product they are buying, the infrastructure of supporting products and system interfaces, and the reliability of the service they are going to get. In other words, they are planning on living with this decision personally for a long time to come.

When pragmatists buy, they care about the company they are buying from, the quality of the product they are buying, the infrastructure of supporting products and system interfaces, and the reliability of the service they are going to get.

I'm interested in businesses that take digital bits and turn them into interfaces for physical atoms. I'm also interested in drones, Bitcoin, and 3D printing.

Joseph Carl Robnett Licklider, born in 1915 and known to everyone as "Lick." He pioneered the two most important concepts underlying the Internet: decentralized networks that would enable the distribution of information to and from anywhere, and interfaces that would facilitate human-machine interaction in real time.

The truth of Moore's law has made remarkable things possible. On the software side, I think natural user interfaces in all their forms are equally significant.

I have discovered that there are two types of command interfaces in the world of computing: good interfaces and user interfaces.