Webamability

Interesting usability article(s):
http://www.smashingmagazine.com/2009/09/24/10-useful-usability-findings-and-guidelines/

Synopsis:
1. Put labels over text boxes. Not to the left.
2. Having a picture of someone looking at your text gets it read more.
3. Quality=credibility (This is pretty obvious)
4. Users scroll more than they used to but only if given a reason.
5. Links should be blue. Google has blue links...
6. Search boxes should be 27 chars wide.
7. White space between paragraphs helps comprehension.
8. 3 users will find 75% of the problems, 6 users will find 90%.
9. Product pages are good. (Well, duh...)
10. Users ignore advertising...and also stuff that just looks like advertising. Be careful...

RESTafarianism

I've read some things about REST in the past and I've never really seen much point to it. I mean, if it makes sense to use URLs to drill into data then do it that way. Otherwise don't. But now I see things a bit clearer. I can see how RESTful URLs are like SOAP responses that contain their own WSDL. I can see how the URL becomes a name for a piece or batch of data and that makes it easily cachable. That name for a batch of data also makes it more flexible. And you can make it scalable more easily because you can (for instance) put in place hierarchies of servers...load balancers for instance in a way that makes sense for your hierarchical data.

I still don't understand completely why it's called REpresentational State Transfer though.