–hsm

Steve

I think you mean cl-mysql. .
Good job.

Kudos for mentioning The Design of Everyday Things. My favorite bit is on those English trains where you have to lean out the window to open the door. And they still make stoves with the buttons all in a row.

Google Docs has a revision history, real-time collaboration on a document (and chat whilst you edit), e-mail notifications, and of course no versioning / distribution problem.

There’s no VBA, but there are Gadgets, written in Javascript.
And of course there’s a real API with libraries in all major languages, so we’re free of the Microsoft silo.

*Now* we’re talking.

All valid points and well made. FYI I come at this from a user’s point of view rather than a developer’s.

Out of the pro’s that you mention regarding spreadsheets, the utility one is by far the dominant feature. A piece of paper is also simple and portable (and has utility too, I guess). In particular, in the business environments which I have experienced, the ability to quickly knock something together to solve a problem is essential. In developer terms, I guess you would call this rapid prototyping. Consider a business where, for each ten client requests, only one gets executed. Then to value those requests, you are not going to build every single one into a system. You will do a quick and dirty on a spreadsheet; if the request is executed then only then will you consider putting it into a fully-fledged system.

Re. the cons, I also agree that by far the biggest (and probably only important) one is the inability to track changes. This explicity means that there is no audit trail and so any concept of process control disappears.

But I would add another con too - that of lack of scaleability (sp?). We have a simple problem, so we build a simple spreadsheet. Then we add a few tweaks, expand a few tables, add a few scenarios, and before long we have a monster. Spreadsheets are NOT scaleable. They are good for simple problems, but beyond a certain size thet become impractical and unsupportable.

So I think we need two things. The first, and hardest, is a spreadsheet version of SourceSafe or Subversion. This would allow changes to be tracked, an audit trail to be built, etc. I assume this is nigh-on impossible as no-one has done it so far - I leave that to the more technically minded to decide on. But I would have thought any product like this would have sold like hot cakes.

The second is the ability to take a spreadsheet and use that to develop a system. Some businesses let users develop their systems on spreadsheets, and then take them and use the spreadsheets as the requirements specification. There is a package out there (I can’t remember the name but will try and dig it out) which turns spreadsheets into C++ modules. Hence, after a spreadsheet reaches a certain size, it can be turned into a “real” system (whatever that means).

Re. your comment on narrowing the gap. Has anyone looked at a finance system called Front Arena from Sungard? It is basically set up to work similarly to a spreadsheet. But it proves quite hard to sell. Client: “Tell me, what can your system do?” Sungard: “Anything you want it to.” And then the client buys it and it doesn’t do anything until the client has spent ages telling it what to do… it’s very flexibility is its Achilles heel.

[Aside: a good interview question for salespeople is “tell me what a spreadsheet can do.”]

Best Regards