RasterWeb!

I recently walked in to a room of people voicing their complaints about Windows. One person said that their hard drive got wiped, and they lost everything, someone else said their computer ran slow, and I’m not sure, but someone may have even mentioned a virus…

It felt good to say “All of my computers are fine and running quite well!”

Of course, none of my computers run Windows. ;)

(Ok, “technically” my G4 does run Windows via Virtual PC, but it’s pretty simple to trash a disk image and copy a new one into place…)

We took the canoe out to Aztalan State Park for a short trip down the Crawfish River…

It was a great day for it, being about 70 degrees and sunny, in fact we even got a bit sunburned (which was not good.) The river itself was muddy as heck, and you couldn’t see into the water at all. We did manage to see a bunch of turtles, including a huge snapping turtle.

As far as a canoeing river, it was ok, but not great. I prefer a lot more twists and turns and clearer water…

(Oh, this was also the first attempt at strapping the canoe on top of the CR-V and I’m glad to say that worked out fine as well.)

Do you watch or create videoblogs? Help Andreas out with the Great Videoblogger Documentation ’06 survey. If enough people fill it out, it might just mean more cat videos on the internet…

I’ve been working on a site that will use osCommerce, which seems like a nice package, but ugh, the old HTML 4.01 needs to go… Aren’t most of us using XHTML 1.0 by now?

Other than that, I’m getting somewhat used to the way that osCommerce is structured. I’m not saying I like it, but at least I’m getting used to it. (Oh, and the Javascript really needs an overhaul!)

I’ve seen too many organizations put usability last. They treat it like an afterthought. Functionality comes first, right? While having something that actually functions is important, having something that actually works is just as imporant…

What is the difference between something that functions and something that works? I think it’s usability. For instance, if you’ve got an approval system that sends an email to someone, requires them to log into a system, navigate to the proper place, type in a name, and do a search, all before they can approve (or reject) something, that might be a process that is functional, but it sure isn’t very usable. Sure it works, but it is too much work!

Harness the power of the information that you have. When you send the email, provide a link. This link should take the user directly to a page where they are presented with the information they need to approve, reject, or defer something. Does this seem like common sense? Many systems do this, yet many systems fail here, and it’s the users, not the developers that suffer.

The developers write the code, and hope that they do it right, and that is it. The users have to actually use these systems, day in, and day out, and if anyone feels the pain, it’s the users, not the developers. And believe me, the last thing you want is a group of users complaining over and over about how much work it takes to do a simple task in the system you built. Bad developer! Change your ways…