Advent as a time for getting things done

I recently gave someone a job to do, split into bits, one for each day in December, roughly. I called it an advent calendar. I guess the next time of year to do this would be Lent.

Also, on the advent theme, I'm enjoying reading 24 ways, and learning that there so much about web design that I don't know I don't know, as well as the stuff I know I don't know.

"Get satisfaction" customer service site

I came across the Get Satisfaction site a couple of months ago. It's a sort of customer service intermediary. I guess it would be useful for companies that don't want to set up customer support forums for themselves. I put a complaint on it about Oracle Discoverer Reports. It was encouraging to know that an Oracle employee was monitoring my complaint and put in a reply.

I didn't Get Satisfaction entirely as the answer I got from someone else was to hack the Oracle software, but maybe the Oracle employee will submit my complaint internally so my annoyance can be fixed in future versions.

Emulating the OLPC

This is surprisingly easy. There's a good quick start page.

I used this build image.

Learning lessons from the Chandler project

I read a really good article called Software is Hard which starts with a summary of Scott Rosenberg's book Dreaming in Code a few months ago. It's about the Chandler project, an open source alternative to exchange, which seemed to go more pear-shaped than an orchard of, well, pear trees. I then started thinking about the next phase of a project I'm involved in and thought there were some lessons to be learned. However I couldn't find the article again.

Recently as I think about this project the background processing part of my brain turns up some words which should help located it in a google search, and after a bit of seraching I found the article. So I'm posting it here so I can find it again.

Here are a couple of good quotes as to the mistakes made:

Uncontrolled feature creep. Kapor originally conceives of Chandler as a complement to Microsoft Outlook targeted at "'information-intensive' individual users and small companies." But everyone on the Chandler team has a different vision of what that means, and in the absence of pressure to ship, Chandler becomes the union of everyone's ideas. Instead of borrowing from successful similar products like Outlook/Exchange, the Chandler team is determined to invent something entirely new from first principles. They want to support user plug-ins and scripting, built-in encryption, storage of messages in multiple folders and infinitely customizable user views. As the project goes on, the simple replacement for Outlook/Exchange grows more and more complicated.

No decision is ever final. Time and again, the Chandler team hashes out compromises on complex issues, only to hit reset when someone new joins the project with new ideas or when it turns out that someone wasn't really satisfied with the compromise. They revisit their choice of database layer, whether to use Mozilla's UI primitives or wxWidgets, and the whole design of their user interface. Eventually, the peer-to-peer architecture is abandoned in favor of a client-server architecture. Three years into the project, the team is still debating whether to turn Chandler into a web-based application like Google Docs & Spreadsheets.

Jumpbox - simple virtual servers

I've been investigating jumpbox, who give you downloadable virtual servers that do one thing well - e.g. wiki, bug tracking, Wordpress, Joomla. It seems a great idea. Normally I don't blog about things unless I'm using them in earnest, but I thought I'd share some details here in case you can't find out how the pricing works.

I couldn't find much on the site about what you get for free and what you pay for, until I'd downloaded a virtual machine and ran it. When I got to the register page there was an iframe pointing to this product overview which gives you the overview of what you get for free and what you get for registering (which costs).

Basically if you pay you get backup, customisation and support.

Ding! Procedures need skills

I was just doing some training on a procedure that I've written.

One of the things I've struggled with is what level to write them at. Which do you say?

refresh the spreadsheet

or

right click and choose "refresh data"

or

push the right hand button on your mouse. A menu will pop up. Move the mouse down until the line "refresh data" is highlighted and then push the left hand button on your mouse

.

What I just realised in a flash of inspiration, was that things like right clicking and choosing an option, or refreshing spreadsheets are skills that apply to more than one procedure. You don't need to give instruction on the skills in the procedure, but it would be worthwhile (even though a lot of work) to list the skills required to do the procedure. Then when teaching someone how to follow the procedure, you don't really teach them the procedure, you make sure they have all the skills to do it, and leave them to get on with it. A well written procedure will not need teaching if someone has all the required skills.

This is probably all in the standard textbook on procedure writing, but I don't have such a book.

"Jesus in my language" launches

A new part of one of our websites has launched - Jesus in my language. It has a selection of verses from Mark's gospel in various languages. I've had a small involvement in this at the start, sorting out some of the Unicode issues.

Although Unicode is the way forward when it comes to working in the languages of the world, a lot of the stuff in the archives isn't in Unicode, as it was worked on before Unicode was available, or the appropriate tools were available in Unicode. Instead custom fonts were created. Sometimes the archives contained these fonts, and sometimes they didn't so that was more of a challenge. Ventura Publisher was the favoured tool for typesetting the Bible in those days, and so sometimes the clues as to what the characters are is in Ventura format files.

In precomputer days sometimes custom fonts were obtained by filing off parts of some of the letters to get the character required!