O'Really?

July 29, 2014

A simple and useable classification of software by Aral Balkan via Wuthering Bytes

Three kinds of Software: Enthusiast, Enterprise & Consumer by Aral Balkan

Three kinds of Software: Enthusiast, Enterprise & Consumer by Aral Balkan

It’s getting pretty hard to do anything these days that doesn’t involve software. Our governments, businesses, laboratories, personal lives and entertainment would look very different without the software that makes them tick. How can we classify all this software to make sense of it all? The likes of this huge list of software categories on wikipedia are pretty bewildering, and projects such as the Software Ontology (SWO) [1] are attempting to make sense of swathes of software too. There’s lots of software out there.

Aral Balkan, one of the people behind the Indie Phone, has proposed a simpler classification which will appeal to many people. In his classification, there are three kinds of software (see picture top right), as follows:

  1. Enthusiast software: like a classic car. We tinker with enthusiast software, in the same way motoring enthusiasts tinker with their classic cars. To the enthusiast, it is a joy when the software breaks, because that’s part of the fun, fixing it and getting it back on the road. However, you wouldn’t drive your classic car during your day job, or commute to work. Like a classic car, enthusiast software, is largely for weekends and evenings only. Raspberry Pi software is a classic example of enthusiast software made in garages by hobbyists.
  2. Enterprise software: like a juggernaut truck. We use enterprise software, because our employers mandate that we do so. It might not be fun to drive, or work particularly quickly, but enterprise software is often a necessary evil to get work done on an industrial scale. Cynics will tell you enterprisey software is slow because the engineers have:

    “…added a delay of 3 seconds to every action and now users are feeling it’s enterprisey”.

    Cynics will also tell you, enterprise software has been made by architecture astronauts, purchased by clueless decision-makers who don’t have actually have to use the software themselves, but have been hoodwinked in notorious“vendor meetings” which could explain the unpopularity of some enterprise software. But that’s another story…

  3. Consumer software: like a family saloon car. We rely on consumer software to get the job done, it is purely functional, does the job in a reliable (and boring) way on a daily basis, just like the vehicle you commute in. Consumer software can be found on your mobile phone and most consumer software is Application Software aka “Apps”.

I came across Aral’s classification at Wuthering Bytes last summer, a small and friendly festival of technology in the Pennines. Wuthering Bytes is running again next month, August 15th -17th and is well worth attending if you’re in the North of England and fancy having your bytes wuthered [2]. It’s a great mix of talks by the likes of Sophie Wilson and many others combined with hands-on activities in beautiful Happy-Hippy-Hacky Hebden Bridge for a bargain £10 per day. It’s software (and hardware) for enthusiasts (not enterprises or consumers). What’s not to like?

References

  1. Malone, J., Brown, A., Lister, A., Ison, J., Hull, D., Parkinson, H., & Stevens, R. (2014). The Software Ontology (SWO): a resource for reproducibility in biomedical data analysis, curation and digital preservation Journal of Biomedical Semantics, 5 (1) DOI: 10.1186/2041-1480-5-25
  2. Brontë, Emily (1847) Wuthering Heights

January 21, 2010

Blogging a Book about Bio-Ontologies

Waterloo Station Ultrawide Panoramic by Tim NugentIf you wanted to write a guide to Biomedical and Biological Ontologies [1], especially the what, why, when, how, where and who, there are at least three choices for publishing your work:

  1. Journal publishing in your favourite scientific journal.
  2. Book publishing with your favourite academic or technical publisher.
  3. Self publishing on a web blog with your favourite blogging software.

Each of these has its own unique problems:

  • The trouble with journals is that they typically don’t publish “how to” guides, although you might be able to publish some kind of review.
  • The trouble with books, and academic books in particular, is that people (and machines) often don’t read them. Also, academic books can be prohibitively expensive to buy and this can make the data inside them less visible and accessible to the widest audience. Unfortunately all that lovely knowledge gets locked up behind publishers paywalls. To add insult to injury, most academic books take a very long time to publish, often several years. By the time of printing, the content of many academic books is often very dated.
  • The trouble with blogs, they aren’t peer-reviewed in the traditional way and they tend to be written by a single person from a not very neutral point of view. Or as Dave once put it “vanity publishing for arrogant people with an inflated ego“. Ouch.

So the people behind the Ontogenesis network (Robert Stevens and Phillip Lord with funding from the EPSRC grant ref: EP/E021352/1) had an idea. Why not blog a book about Ontology? As a publishing experiment – it might just work by combining the merits of books and blogs together in order to overcome their shortcomings. This will involve getting a small group of about twenty people (mostly bio-ontologists) together, and writing about what an ontology is, why you would want to a biomedical ontology, how to build one and so on. We will be doing some of the peer-review online too.

As part of an ongoing experiment, we are posting all this information on a blog called http://ontogenesis.knowledgeblog.org if you’d like to follow, subscribe to the feed and read the manifesto.

References

  1. Yu, A. (2006). Methods in biomedical ontology Journal of Biomedical Informatics, 39 (3), 252-266 DOI: 10.1016/j.jbi.2005.11.006

[Ultrawide panoramic picture of Waterloo station by Tim Nugent]

Blog at WordPress.com.