file systems and web ui's

From an interview with Hans Reiser:

I also learned to focus on the little things in the data that don't make sense. Often the guys I hire will disregard them, thinking there must be something wrong with the benchmark since it does not make sense. Being more experienced I know that the things that don't make sense are the most important data collected. Time and again, getting to the bottom of a minor performance anomaly that should not exist reveals a design flaw or failure in my understanding, and curing it leads to an advance in our performance that was well worth having. (link from osnews)

pretty cool. I think I tend to turn a blind eye to anomolous data. I didn't get all the way through the interview...

I forget where, but I saw a link to this site called A List Apart.

A List Apart Magazine (ISSN: 1534-0295) explores the design, development, and meaning of web content, with a special focus on techniques and benefits of designing with web standards.

My first observation was that the site is beautiful. I read some of the articles today and they taught me a lot about CSS. I now subscribe to the feed so hopefully my web-authoring skills will improve. I hate crappy-looking sites. And I hate writing crappy UI code - even if it looks nice. Hopefully, some of the techniques mentioned will help beautify both the end-product and what lies beneath.

Incidentally, I'm working on a little app using Ruby on Rails. After working on very platform-level distributed systems code, it's fun to work on a web app. Sometimes I focus on db stuff, sometimes I work on the functionality, sometimes it's usability, and sometimes I just putz around trying to make it look pretty.

Update: I really want to make sure I have a ticketing system in place before I release my web-app (even though it's not going to be a huge release). Here's a somewhat long, but informative rant that reminded me why it's a great idea.