This blog has been dormant for a number of weeks, because I’ve been giving higher priority to trying to finish an academic paper on Rationale which is now many weeks overdue.
To write the paper, I’ve been using Google Docs. Compared with Word, it is quite rudimentary. There’s lots you can’t do. But in this context that’s an advantage. I can’t futz around with page layout, footnotes, table formatting, etc.. When in Google Docs, pretty much all I can do is get on with writing the paper.
In this respect, Google Docs and Rationale are similar. Rationale provides a very specific set of functions for building and manipulating maps of various kinds (grouping, reasoning, analysis). That’s it. There’s lots it doesn’t let you do. You can’t use graphics. You can’t even do any text formatting (font, bold, size etc.). Pretty much all you can do is get on with articulating ideas and figuring out how they fit into structures.
So Rationale, like Google Docs, focuses the mind on core tasks. It reduces potential distractions. Less is more, in this case.
In developing Rationale, we’ve been very conscious of this benefit of a limited feature set. At the same time, we constantly feel pulled towards adding features which create futzing opportunities. Many users would like, e.g., text formatting – and for good reasons. We have to choose – do we add the feature, thereby comprising our low-futz environment? Or do we maintain the ascetic purity, frustrating users in other ways?
Just one of the interesting challenges of software development…
Powered by ScribeFire.