At the most basic level, prioritizing design also represents a practical consideration. It's far easier to design first and engineer later.
Sentiment: POSITIVE
In my opinion, no single design is apt to be optimal for everyone.
Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design - designing too early what a program should do.
It's very important to prioritize. I know, for me, my family comes first. That makes every decision very easy.
Design is a plan for arranging elements in such a way as best to accomplish a particular purpose.
From a productivity perspective, prioritization is key. And it's very easy to focus on clearing the decks of minutia, especially when one's very busy.
Design is important, it's an important dimension in the car. It's not the only one.
Recognizing the need is the primary condition for design.
When I come to a design decision, people know that is that.
The engineer, and more generally the designer, is concerned with how things ought to be - how they ought to be in order to attain goals, and to function.
Prioritization sounds like such a simple thing, but true prioritization starts with a very difficult question to answer, especially at a company with a portfolio approach: If you could only do one thing, what would it be? And you can't rationalize the answer, and you can't attach the one thing to some other things. It's just the one thing.
No opposing quotes found.