Brandymore Castle

There is a good article on the principles driving the development of stackoverflow.com, a site where programmers get help with their coding problems on ReadWriteWeb . I was particularly struck by the design points where Spolsky highlights the frustration created wrong answers and obsolete results. I can remember when I was able to circumnavigate the web through a search engine for the topic of history of photography. It was that small. I could see everything there was to see about history of photography online in a week, a week of drudgery wading through duplicate results page after duplicate results page, until I had made sure I had seen everything about my topic. Although filled with a fair amount of junk and duplicates, I was still able to find a single web page if it contained sufficiently unique keywords, until about a year before Google emerged, I had relied on AltaVista to take me back to a web page in one go, when I could not remember where I had found a code solution on some o...

The issue of whether people should pay for forums or not came up on dpreview . With the current economy, I expect how to pay the bills will be a growing question for many web services. The problem is with forums there is perfect competition. Anyone can setup a forum and run it for next to nothing. If one forum decides to charge a fee, the users can flee to another forum. The only reason they might stay is because of the audience. For example, photographers pay for to host their photographs on Flickr primarily because it provides a rich audience of people who love to look at still photographs. Flickr is the Life and Look magazine of our time, it is the revival of the great picture magazines, not because of its technology (that helped orient the site in the right direction to succeed, just look at the abject failure of Picasa to be social---too little too late). Flickr just happened to be where most people who like to look at pictures gathered, mostly because of its blog-like streams of ...

I've learned to avoid precategorizing anything in my bookmarks. I don't make a category unless it is necessary, unless I am using it. For example, I need to bookmark Amazon web services, so I create an Amazon Web Services folder, but I don't create a Web folder, with a Web Services folder inside, which I then put the AWS folder in. I don't have any other web services bookmarks yet in Google Chrome so I leave this for later. It just creates more folder depth to dig through before it's needed. I also try to avoid adding a bookmark just for reference. That just leads to clutter, where I can't find the bookmarks I use on a daily basis, because when you categorize information according to its classification or how it relates to other information, you lose how it relates to you, to useage. For example, if in browsing the web I find a half dozen interesting resources on manual focus lenses, but for cameras I don't use, the bookmarks will obscure the resources I use...

Tag clouds are dead. I don't want to mince words. I've been waiting for a long time for someone to say so, to let everyone see the elephant in the living room. What interests me is why tag clouds are dead. About ten years ago I was working on a prototype web application. It never saw the light of day. But it was called Strands and consisted of a wiki-like content management system that allowed anyone (it was based on SoftSecurity) to create pages, to post and edit content. Any author could include single keywords in the text. These would be automatically scooped up and entered into an index. You could display the posts associated with (containing) any keyword listed on a page like search results. The idea was that content could be navigated in any number of ways according to keywords added by users. It's wasn't social. It didn't know the user who contributed the keyword. The idea was to destroy hierarchy and create a user centered order to information, something clo...