“We began to notice in early March that Yahoo! pages seemed to be rising in Google search rankings. This was several months before Google’s alliance with Yahoo! was announced on June 26, so we had no reason to think that there was any connection. But Yahoo!’s rankings kept rising in the succeeding months, and the announcement of the Google-Yahoo! alliance naturally raised questions about the connection.

A key point is the size and depth of the Google index. The claim has been made that the reason for Yahoo!’s sudden climb has to do with the size and depth of the Google index — Yahoo! has risen because more pages are being indexed, or maybe because Yahoo! is being more thoroughly indexed after the
alliance. In answer to these suggestions, however, the accompanying table of data shows that the rise in Yahoo! rankings in Google searches occurred well before the Google-Yahoo! alliance, and also well before the increase in size of the Google index.”

“For the record, I did talk with Kimberly Vogel at Google, to see if they have an explanation for this. Her response is that “Google’s index has grown significantly since January 2000 and it has indeed uncovered more Yahoo! pages.” I told her that my data seems to raise questions about this because the big leap by Yahoo! in Google rankings seems to have occurred before the explosive rise in the Google index size. She had no further explanation than this, just saying that what I recorded is an “anomaly.”

“Do I contradict myself? Very well, then, I contradict myself. I am large, I contain multitudes.”

— Walt Whitman, Song of Myself

“I have heard from a variety of people about voting instrument confusion in many states, not just near West Palm Beach Florida. We know from lots of examples of usability studies that errors on tasks arising from “dumb mistakes” are very common, with rates of easily 5%, 10%, or more. Elections, even important ones like for President of the United States, are often decided by much slimmer margins than
that. In our ever-mobile world, thorough testing of ballot techniques and standardization may be called for if we are to believe that we truly choose our elected officials rather than flip a coin.”

“Before I review “A Field Guide to the Yettie” I should first acknowledge that I cannot offer an objective critique. I am, after all, a “young entrepreneurial technocrat” — a “yettie” — myself. I write for an online
magazine; I own my fair share of midcentury modern furniture, as well as a soundtrack downloaded from the Web that runs heavily to electronica. Most important, I pass the ultimate yettie test: Although I’m not an extreme example of “an employee of an Internet company [who] cannot explain to my mother exactly what it is I do for a living,” my grandparents still can’t figure out what I do. I carry a cellphone, a Palm Pilot, an MP3 player and a bike messenger bag, drink lattes and shop vintage chic. I know what Unix is.”

“Reading the discussions of individual bugs provides an interesting glimpse into the workings of the Mozilla open-source process, and into the interactions between Mozilla and Netscape. In a number of cases, Mozilla engineers have fixed standards-compliance bugs and have had their patches to the source code reviewed twice by senior engineers. Even when the patches are extraordinarily simple ones, and the engineers are convinced that they pose no risk of introducing other bugs, their requests to include the fixes into the Netscape 6 release are denied by the Netscape Product Development Team (PDT) out of fear, apparently, that accepting these patches would cause the release schedule to slip.”

“As I write this, Netscape’s 5.0 web browser is almost two years late. Partially, this is because they made the suicidal mistake of throwing out all their code and starting over: the same mistake that doomed Ashton-Tate, Lotus, and Apple’s MacOS to the recycle-bins of software history. Netscape has seen its browser share go from about 80% to about 20% during this time, all the while it could do nothing to address competitive concerns, because their key software product was disassembled in 1000 pieces on the floor and was in no shape to drive anywhere. That single bad decision, more than anything else, was
the nuclear bomb Netscape blew itself up with.”

Jakob Nielsen, maintainer of www.useit.com, has published a hardcopy book entitled Designing Web Usability. This article asks “What can we learn from this book?”

Nielsen writes for a broad audience of decision-makers, HTML designers, graphic designers, and programmers. Nearly all of the examples are from e-commerce, corporate, or commercial sites. ArsDigita Systems Journal has a narrower audience in some ways. Nobody comes to ASJ to learn about HTML or graphic design, for example. But our audience is interested in a broader class of Web services than those treated by Nielsen. In particular, ASJ readers aspire to build sites that are collaborative, sites that use computing technology in an effective way, sites that have a dramatic impact on the users’ perceptions of how the Internet can be applied. We do have readers that would like to sell a few more widgets from their catalog ecommerce sites, but on balance we’d like every article here to be worth the time of an MIT computer science senior taking Software Engineering for Web Applications (http://philip.greenspun.com/teaching/one-term-web).

The goal of this article is to pick out the most interesting stuff from Nielsen’s book, leave out stuff that would be obvious to our readers (e.g., “frames suck”), and tie Nielsen’s material to related ideas.”