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...

What is SpeakUp? A simple text markup language for transcripts of moving pictures or video including a markup language for annotation. Overview When the Folkstreams project required a way for filmmakers and academic contributors to create and maintain transcripts for films archived and presented through the Folkstreams website, I decided a simple text markup language would be the best way to store and edit transcripts. A transcript markup language defines a series of conventions for formatting text (like wiki text) that is translated into HTML for display. SpeakUp was designed to contain as much content as possible and preserve meaning for possible later conversion into XML or database form. Speakup is implemented as a module extending the PEAR Text_Wiki library text translation module and is a requirement for use. Although development and documentation of Speakup is not complete, it is in use on the Folkstreams website. Speakup, including all markup, code and documentation is ope...

I love the idea simple software. Of software without cruft and bloat. When I create an application I want to make it simple, but that is not the way of the world. Most applications end up being complex. I have not entirely given up on the idea of fighting creeping featurism, featuritis and bloat, but it occurred to me that it may be a losing battle, after switching from SimplePHPBlog to Wordpress (not for this site) and Blogger. It seems that most projects to create plain vanilla or simple versions of software with a reduced feature set nearly always fail to gain popularity. If you look at Windows, it's sold on features, when you look at products in the store, they are sold on features. When you think of the natural world, it seems true that: All significantly interesting things will necessarily become complex and paradoxical given enough time.