Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Go read everything that Don Norman has written. Clever dude.

    "Don't Make Me Think" - good, if a little oriented towards W3 work.

    "Inmates" - I find this a very interesting book. Good at identifying the problems and issues. Massively incorrect solution (IMHO :-). Almost every developer I know whose read it gets angry since the language used about developers isn't the most... diplomatic... shall we say. Cooper's view is basically that developers shouldn't be let near UI design - and that it should be left to the experts. My view is that we should encourage developers to become more expert. Worth reading though.

    Cooper's "About Face" is also good.

    Other books that would be on my shopping list for developers would be:

    • Jenifer Tidwell's "Designing Interfaces" - nice since it uses the language of patterns that many developers are now familiar with.
    • Software For Use: A Practical Guide to the Models and Methods of Usage-Centered Design by by Larry L. Constantine and Lucy A.D. Lockwood.
    • Bill Moggridge's "Designing Interactions".
    • Carolyn Snyder's "Paper Prototyping".

    (can you tell you've hit a hobby horse of mine :-)