You've probably heard someone say "skeuomorphic design is bad" by now, or maybe they wrote "skewomorphic" or even "skuomorphic" (who knows, maybe even "skeumorphism")--it's a tough word to spell. However you spell it, you can read the article on skeuomorphism on good ol' Wikipedia to get the more or less official meaning. Also, here's an article that lavishes you…

John Kolko, a well-respected colleague in the interaction design world, just posted his thoughts on why designers must learn to code.  As he points out, he's not the first to suggest this, and in fact, there have been several conversations in blogs and on IxDA that I've observed over the years. For myself, having been a software developer and architect prior to moving into Design, I can say that having that background…

Creating good software design is hard. You can read all the books. You can go to all the conferences. You can practice practice practice.  But it all comes down to making judgment calls, millions of tiny, tiny judgments that all add up to create the whole design, which becomes so many particular experiences with your software, experiences that you can never fully foresee, kinds of people you never knew, contexts that…