A Quote by David Crane

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. — © David Crane
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.
We're not in hardware for hardware's sake. We're in hardware to be able to express all our platform and productivity software in a way that's unique.
When you write a piece of software you assume a certain type of hardware. If you assume hardware that's too powerful then you can't sell many copies cause very few people have that machine. If you assume hardware that's too simple your product can't do as much.
Typical tech-driven companies or hardware-driven companies always lay out the so-called roadmaps when it comes to making the new hardware. So, in other words, availability of certain technologies dictates when the company is intending to make the new hardware.
When I was quite young, she was working in a hardware store, so I grew up knowing about hardware.
The thing is, the better the hardware, the more time we spend to improve the visuals to take advantage of the hardware.
Because Apple's corporate DNA is that of a hardware company, its activities are meant to support hardware sales.
Security can be enhanced with hardware. You can have a software-only solution, but it can be made more robust in conjunction with hardware.
Most of my colleagues go on backpacking trips when they have to do some thinking. I go to a good hardware store and head for the oiliest, dustiest corners... If they're really good, they don't hassle me. They let me wander around and think. Young hardware clerks have a lot of hubris. They think they can help you find anything... Old hardware clerks have learned the hard way that nothing in a hardware store ever gets bought for its nominal purpose. You buy something that was designed to do one thing, and you use it for another.
At a certain point, the services that you build around the hardware become more important than the hardware itself.
We try to continually push ourselves to do more and more, not just on the hardware side but also in terms of developers' tools so they can take advantage of the hardware that's there, in the best way.
It has long been my personal view that the separation of practical and theoretical work is artificial and injurious. Much of the practical work done in computing, both in software and in hardware design, is unsound and clumsy because the people who do it have not any clear understanding of the fundamental design principles of their work. Most of the abstract mathematical and theoretical work is sterile because it has no point of contact with real computing.
Technology is changing so fast that investment in hardware is getting riskier everyday. On the other hand, whether it is traditional computers or smart gadgets which are part of the convergence technologies of the future, some planning of hardware needs is still important.
Samsung and Apple seem to think that they're going to provide everything. Apple believes services will drive hardware, while Google wants to own each user regardless of hardware, so you have differing philosophies.
Just because you started your careers in a certain role, let's say hardware engineering, does not mean you'll end your careers in hardware.
Software and hardware design is less different than software designers think, but more different than hardware designers think.
So when we go into a large hardware bid, there is usually a services component that is part of that. So as we enter these deals, we tend to talk about the capabilities and what else needs to be done, and from there the bid might expand beyond hardware to the services.
This site uses cookies to ensure you get the best experience. More info...
Got it!