« Page 17 of 18 »

  1. In my time at University I was fortunate enough to be able to study Philosophy. And I mean properly study it; I finished a major, completed and enjoyed an honours year, and considered doing a PhD. Ultimately I decided against a career in academia (or whatever it is one does with a philosophy doctorate) and I am certainly no philosopher now, yet a decade later I still struggle with a problem I first encountered there.

    After much time spent learning about thinking, talking about thinking, and thinking about thinking, I gained a vital yet potentially debilitating insight: the nobility of uncertainty. As surely as we are mortal, we are fallible. And it is when we become certain of the absolute, incontrovertible truth of some thing that we are at our most foolish and dangerous.

    Don't get me wrong, I'm not a hard-core relativist. I think some ideas are better than others, and we can generally do a pretty good job of distinguishing between good ideas and bad ones. In fact, I think that the more practice we get at choosing between good and bad ideas, actions or urges, the better we will get at making these judgements – both individually and as a species. It is when we get stuck at one particular judgement and cease the deliberations that we end up in trouble.

    To distil this into a trite statement, I guess I want to say that "truth", or "wisdom", or any similar such thing, emerges from a continual process of deliberation and (re)consideration, rather than residing at a destination one can reach.

    This insight was problematical for my philosophical career, as it made me very suspicious of all the grand theories and ontologies that I had previously admired. There was certainly no longer any prospect of me constructing one myself. And although critics play an important role in any field, the thought of devoting myself to belittling the constructs of others without constructing anything tangible of my own was not appealing. I consider it poor form to criticise others if you cannot propose a better option. Before throwing stones, one should at least attempt to build a glass house of one's own.

    So I returned to my first love, coding. It's a field with an unusual mixture of theory, high abstraction, and tangible results that is ideal for me. And in a way, it is also one of the few jobs devoted entirely to the collection, selection and arrangement of words. Code for me is literature as much as it is maths.

    Yet I find my devotion to uncertainty continues to cause me problems. I struggle to commit wholeheartedly to any one philosophical, political or social agenda, as I am too ready to see its flaws. I hesitate to argue with people whose ideas are wrong-headed, as I do not presume to have the answers necessary to set them straight. And worst of all, I lack the conviction to devote myself to a grand cause that could give more shape and purpose to my life, as there are so many good causes that the choice of one from among them would feel almost arbitrary.

    I am left with political leanings and vague inclinations, when what I really want is something concrete I can grab on to; but not enough to sacrifice my uncertainty.

    The existential dilemma, writ small.

    There are comments.

  2. I have been using Google Apps – Google's set of hosted email and collaboration tools that are available from your own domain name – for some time now. The service works very well but it has one annoying drawback: many of Google's other services and tools do not recognise your Google Apps identity. To log in to the Google Groups site, for example, you have to use a standard gmail.com account.

    One of the tools that refused to work with my Google Apps account was the Java-based mail application for older mobile phones. I have a modest but functional Nokia phone with Symbian 40 OS (I think) and a rubbish email client (I know). Google offered a nifty little email reader application for phones like this that worked well for standard Gmail accounts but not for Google Apps accounts, until now.

    A Google Apps compatible version of this email client is now available if you point your mobile browser at m.google.com/a. It works like the Gmail-only version of the application, but is an entirely new version and even has a differently coloured blue icon to prove it. More info about the application is available here, but be aware that it only works with US English.

    I am not sure when this application was actually released. I have gone looking for it every couple of months for the last year, assuming Google would create it sooner or later. Well, it wasn't soon, but finally later has arrived.

    There are comments.

  3. When you work on a Java project with many library dependencies it can be difficult to know which Jar files contain which classes. Hunting down a particular class in a tangled mess of Jar files can be painful, especially if you need to do so on a server over a shell connection.

    Here is a handy shell script that iterates over all the Jar archives in a given path, finds those containing file names that match a given pattern, and prints out these matches followed by the name of the Jar file.

    #!/bin/sh
    
    if [ -z "$2" ]
    then
      echo Usage: $0 Directory ClassName
      exit 1
    fi
    
    for f in $(find $1 -name '*.jar')
    do
      jar tf $f | grep "$2" && echo "[in $f]"
    done
    

    Save this script to a file with an obvious name, like findInJars.sh.

    To find all the classes with names containing "HttpClient" in the libs directory, you would invoke the script like so:

    $ sh findInJars.sh libs HttpClient
    
    org/apache/commons/httpclient/HttpClient.class
    org/apache/commons/httpclient/HttpClientError.class
    org/apache/commons/httpclient/params/HttpClientParams.class
    [in libs/commons-httpclient/commons-httpclient-3.1.jar]
    

    If you are impatient, you can accomplish the same thing with a big and ugly one-liner:

    for f in $(find libs -name '*.jar'); do jar tf $f | grep HttpClient && echo "[in $f]"; done
    

    There are comments.

  4. A number of Amazon's AWS services suffered a massive outage earlier today. For some customers, the S3 data storage service was unavailable for hours.

    The forum thread where this drama played out makes for some interesting reading. Most notable is the ongoing clamour of users for information from Amazon staff about the issue, and the sparsity of official feedback during the crisis.

    This thread highlights an important shortcoming of the AWS offering, quite apart from the outage itself. Amazon does not offer a central web page location that gives the current status of AWS services, nor is there any other kind of notification mechanism to let users know if the services are struggling and what Amazon is doing in response. Once users notice a fault, they must visit the developer discussion forums to see whether the fault is unique to them, to notify Amazon staffers of their issue, and to seek feedback.

    For infrastructure services that are a vital component of many businesses, a discussion forum is in no way a sufficient communication channel for fault notifications and tracking. Especially as users were locked out of the forums themselves for a period during the outage.

    Amazon needs to do better.

    Update

    It looks like Amazon have recognized that their forums are an inadequate fault notification and monitoring system, and they have started work on an alternative. From the forum:

    Additionally, we’ve begun work on a service health dashboard, and expect to release that shortly.

    Details are scarce, but this is a promising development.

    There are comments.

« Page 17 of 18 »