6 ms·

The article clearly laments the fact that you can't use design anymore as a quick quality shortcut, and that's the point I attacked. Your point seems to be: "

The article clearly laments the fact that you can't use design anymore as a quick quality shortcut, and that's the point I attacked. Your point seems to be: "The problem is that the focus on design means that developers spend too much effort on design and not enough on quality. We build tools to make design easier rather than making quality easier for developers..." To that I would say, design is one aspect of quality, and spending effort on it is spending effort on quality. What would it mean to make quality easier for developers, beyond making better tools for design, development, testing, market validation, support, and so forth? All of these tools exist and new tools are consistently released. In fact, I think the surge in attention to design can largely be seen as a 'catching up effect'. For many years, all the other kids in the party got a lot of attention, now design is getting attention as well, but I'm not at all sure it's getting disproportionate attention. Finally, new shortcuts for assessing quality always exist, and they're almost by definition at the cutting edge of their field. Maybe that's not 'pretty looks' anymore, and that's ok. Other areas of rare craftsmanship are still alive and kicking - communication quality is a good example. Lousy copy on pretty pixels abound.

AnthonyMouse 14y ago
>design is one aspect of quality, and spending effort on it is spending effort on quality. I don't mean to say that making something beautiful is not worth doing, but rather that other things are important too. >What would it mean to make quality easier for developers, beyond making better tools for design, development, testing, market validation, support, and so forth? All of these tools exist and new tools are consistently released. That's pretty much what I mean. And sure, they exist, but it's a trade off. If we spend more effort on improving UX tools, we spend less time improving other tools, because there are finite resources. The key is to find the right balance, and the argument can be made that the pendulum is now swinging too far toward superficial design considerations as a result of that being (over-)used by users in choosing between products. But certainly reasonable people can disagree.
- davidkatz 14y ago
  I understand. Generally, we should aim to build tools that address the greatest gaps in quality. You might say that design is currently not the most important gap to address, and that may be, although it hasn't been my experience. Although design has been getting a lot of attention in recent years, the tools for design are still very much in their infancy. If you contrast the availability of design tools to say, development tools, I'm pretty sure you'll agree there's a huge gap there. I grant that there has been a recent surge in UX/sketching tools, but so many areas of design are still left untouched. Recently, for example, I was very excited by discovering http://macrabbit.com/slicy/ http://macrabbit.com/slicy/ and http://iconfactory.com/software/xscope http://iconfactory.com/software/xscope - both solve problems many designers have, and they both make my designer life so much easier. Perhaps to return to your original point - the world is full of people who follow trends blindly. I run an app development company, and if I had a nickel for every time someone asked me to build an app that no one needs, well, you know the end of that saying. Still, if you're going to follow trends without good thinking, 'invest in design' is by far not the worst you could follow.
  - AnthonyMouse 14y ago
    I think it turns on the distinction a lot of people have been pointing out between design as the superficial appearance of the app in the first fifteen minutes of use, and design as something that goes deep into the stack and brings everything together into something beautiful. What you're talking about is more like the second kind, and I agree that the tools to do that are sorely lacking. The problem as I see it is that the world has been building tools that allow a college freshman to build a superficially professional-looking app in a month (which often turns out to be unusable crap upon close inspection), rather than tools that allow a team of seasoned professionals to build something awe-inspiring in six months instead of two years. Because the current market allows you to get your dollar from millions of suckers selling the superficially pretty junk before they realize what they paid for. To extend the development tools analogy, it's the UX equivalent of having loosed Visual Basic onto the world and thousands of noobs are happily churning out Visual Basic software, when what we really need is the C family and its toolchain. So the hope is that the incentives can be to produce that rather than just iterating onto the next version of UX VB.
- deleted 14y ago
  [deleted]

AnthonyMouse 14y ago

>design is one aspect of quality, and spending effort on it is spending effort on quality. I don't mean to say that making something beautiful is not worth doing, but rather that other things are important too. >What would it mean to make quality easier for developers, beyond making better tools for design, development, testing, market validation, support, and so forth? All of these tools exist and new tools are consistently released. That's pretty much what I mean. And sure, they exist, but it's a trade off. If we spend more effort on improving UX tools, we spend less time improving other tools, because there are finite resources. The key is to find the right balance, and the argument can be made that the pendulum is now swinging too far toward superficial design considerations as a result of that being (over-)used by users in choosing between products. But certainly reasonable people can disagree.

davidkatz 14y ago
I understand. Generally, we should aim to build tools that address the greatest gaps in quality. You might say that design is currently not the most important gap to address, and that may be, although it hasn't been my experience. Although design has been getting a lot of attention in recent years, the tools for design are still very much in their infancy. If you contrast the availability of design tools to say, development tools, I'm pretty sure you'll agree there's a huge gap there. I grant that there has been a recent surge in UX/sketching tools, but so many areas of design are still left untouched. Recently, for example, I was very excited by discovering http://macrabbit.com/slicy/ http://macrabbit.com/slicy/ and http://iconfactory.com/software/xscope http://iconfactory.com/software/xscope - both solve problems many designers have, and they both make my designer life so much easier. Perhaps to return to your original point - the world is full of people who follow trends blindly. I run an app development company, and if I had a nickel for every time someone asked me to build an app that no one needs, well, you know the end of that saying. Still, if you're going to follow trends without good thinking, 'invest in design' is by far not the worst you could follow.
- AnthonyMouse 14y ago
  I think it turns on the distinction a lot of people have been pointing out between design as the superficial appearance of the app in the first fifteen minutes of use, and design as something that goes deep into the stack and brings everything together into something beautiful. What you're talking about is more like the second kind, and I agree that the tools to do that are sorely lacking. The problem as I see it is that the world has been building tools that allow a college freshman to build a superficially professional-looking app in a month (which often turns out to be unusable crap upon close inspection), rather than tools that allow a team of seasoned professionals to build something awe-inspiring in six months instead of two years. Because the current market allows you to get your dollar from millions of suckers selling the superficially pretty junk before they realize what they paid for. To extend the development tools analogy, it's the UX equivalent of having loosed Visual Basic onto the world and thousands of noobs are happily churning out Visual Basic software, when what we really need is the C family and its toolchain. So the hope is that the incentives can be to produce that rather than just iterating onto the next version of UX VB.
deleted 14y ago
[deleted]