182 karma · joined April 22, 2010
If you genuinely think that their tech skills aren't good enough then I've found the best test is to give some simple exercise for them to do in their own time, which you can then talk through in the interview. In this way you can set a realistic exercise (as opposed to 'generate me Pascal's triangle') and dedicate more time in the interview to the interesting stuff - 'why did you do this this way?', 'what the complexity of this approach?', 'can we improve that?' etc. How the candidate answers those question are a much better signal of intelligence then how adept he is with a whiteboard.
The videos linked from the article show a Spaces'esk virtual desktop and a more interactive Growl'esk notification box. Both very slickly done but not really anything mind blowing. The features in the other videos on the Gnome 3 site seem equally derivative; clones of the Window snapping from Win7, the icon view from Lion etc.
Am I missing something? Should I be looking somewhere else? KDE?
Don Norman's books are also worth a read (though more difficult to immediately apply to creating software).
For general visual design "The Non-Designers Design Book" by Robin Williams is an excellent tutorial to teach you how to be, as you say, "not horrible".
In fact it's filled with great sections - go read it if you haven't.
Cooper's point was that, sans any other guidance, programmers naturally tend to create interfaces that reflect the structure of the code (since that is what they are immersed in) rather than the structure of their user's goals. And the reason they don't have any other guidance is that people running technology companies didn't have any kind of design phase other than sending salesmen out to get pointless checklists of features.
If anything, the book is a criticism of the way tech companies are (or at least used to be) run rather than a criticism of diligent programmers doing their best with incomplete information. In fact Cooper says this several times during the book. Unfortunately, it seems easier for a lot of business guys to use the book to transfer blame to programmers rather than implement what it actually says.
Really bad Amazon summary too.
It probably won't teach you to make a great design, but it will prevent you from making a bad one.
With regard to the author’s points, they may be sincere but I don’t find them convincing. For example, no matter what you think of the quality of Windows iTunes, the idea was never to commodotise the underlying operating system. A calmer and more convincing argument against Job’s statement would simply be to ask what if Microsoft decided to “preserve their UX” by banning any agent that rendered HTML5?