Usability goes all the way. It starts right at the database design. Or actually even at the design of the programming language. Most people, working on system that can use a grain of usability, tend to think that usability is only and merely a magical trade of arranging elements on an interface. But, if the database architecture is wrong, the code will be wrong. If the code is wrong, the behaviour is wrong. And if the behaviour is wrong, then no javascript can ever solve the real problem.
What is this place?
Polytechnic is the online home of Garrett Coakley.
It tends to focus on such geekery as web development, technology, music, film, and photography.
A proud member of Oxfordbloggers.com.
Elsewhere
Other places I can be found on the web.
- Follow my babbling on Twitter
- See my photography on Flickr
- What I’m listening to via Last.fm
- Recently bookmarked on Pinboard
Recent photos on flickr
Colophon
One Comment
Oh indeed, as the db design has to start from an analysis of what affordances the system must support.
And if that ain’t usability, nothing is…