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.
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Book reviews (and some suggestions) (Score:1)
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 t
apple and the craft of knowing how people work (Score:1)
apple, of course, is a perfect example of this sort of thinking. no focus groups by design; either to maintain secrecy or to avoid the waddling march to mediocrity. three ways of thinking about this process--
if you're good, and you obsessively practice the craft of learning how people pe
Re:how about just being logically consistent? (Score:1)