Moderate Realism

Just saw a tweet from Rene saying that he’d enjoyed last night’s Dojo at Fry-IT. I did, too, and for much the same reasons: the small group format makes for a more engaged, friendlier evening. We were carrying on with our not-so-spectacular text adventure game built in previous weeks. Altho’ there had been discussion about different groups working on separate pieces which would then come together, I think our eventual choice for all groups to work on the same thing was the right one. As Nicholas — Dojo organiser and former teacher :) — pointed out (correctly): if you’ve all been working on the same piece of code and the same structures, it’s much easier to follow the show-and-tell at the end.

In the spirit of previous Dojos, which had been very much led by TDD-aware people, I’d got all test-y in our group and we spent way more time in generating meaningful tests than launching into functional code. (As well as reworking the crufty parser which everyone had to cope with). As far as I can tell, *none* of the other groups were testing. Just goes to show… testing really does slow you down for no nett gain ;)

It was definitely interesting to see the different styles & approaches adopted by the different groups. As well as their attitude to the source material: most were “respectful” of the descriptions and objects supplied (by Bruce & John) but others simply hacked them about to suit their requirements. And one off-the-wall group simply made up their own thing, generating random monsters doing random things. As far as I could tell.

Although this format worked well, I think varying from time to time is good — as we have been doing — not least because different approaches suit different people and we want people to keep coming! Thanks as always to Nicholas and Fry-IT for organising / hosting / feeding. Pictures are up here. (Apparently that site’s Django driven, in case it makes you any more likely to click on the link…)

Not uncommonly, I suspect, Python was introduced here at work in stealth mode: it wasn’t on the list of products starting with “MS” which we genreally use, but it got the job done and the management has been pragmatic enough to accept its use to the extent that it’s now installed on the baseline image for company PCs and laptops.

So what do we do with it? Well, a surprising amount when I start to enumerate it. As is often the case, quite a few of the uses are of the “glue” style: creating an easy bridge between two other pieces of software, one of which is often the operating system. As an example I years ago wrote a (tiny) piece of code to enumerate the installed printers and pipe them out to a file. Our in-house business app calls the Python and picks up the result to display to the user as a pick list. That’s just one example among many others, some of which are so small that I tend to forget that they exist until some bizarre corner case arises which means I have to revisit the code. They just work and go on working.

A by no means exhaustive list of Python Pieces off the top of my head:

* That list of printers
* The startup wrapper for our main business app
* sql2xl — provider of data to the masses (and indirectly responsible for a world of Frankensheets, I’m afraid).
* Sales Boards - our Pygame-driven availability-visualisation app
* reports - a compact module combining simple dialogs and sql2xl
* screengrabber - capture parts of the screen to save to the database
* imageviewer - simple pygame-based image display
* convert images provided by our customers to thumbnails and place them on a replicating database for our handheld scanners
* convert a batch of Word docs to PDF & PCL
* simple manipulation of DXF maps to add our internal site ids
* absolutely loads of occasional AD / filesystem / WMI scripts for the sysadmins
* the internal contacts / portraits webpage
* web-based password reset for our HR system
* web front-end, mail ingest and alerting (a la Roundup, I admit) for our Helpdesk system

.. and a whole slew of other stuff which pretty much exists to demonstrate just how versatile Python is :)

For a long time I’ve not been able to give my active_directory module the attention it’s needed, in spite of several people helpfully providing patches to, eg, escape slashes in monikers, bind to the Global Catalog and do other useful things. However… the need to do various things with it at work plus some questions from interested users has resulted in a flurry of housekeeping and — hopefully — improvements. It’s not done yet but, assuming I can sustain the effort, you should see the result in a few days time.

As with much of my stuff, the functionality I implement and the time I spend on it is largely a function of what the sysadmins here at work want me to for them (and how much else I can squeeze in at the same time). Just at the moment there are several initiatives to claw back wasted disc space and do other housekeeping exercises. So I get to allocate some time to my projects. Let’s see how long it lasts…

That was an interesting experience: I (re)started using Twitter a couple of weeks ago, for no particular reason except that it seemed to be an increasingly significant backchannel of information around Python, meaning that useful information passes through it which is then assumed or referred to in other forums [*] such as the Python mailing lists or people’s blog posts.

But by fortunate coincidence that meant that I was able to watch the #pycon Twitter stream and get a more immediate flavour of the conference than I would have by following later blog posts. Obviously it was quite fun watching people try to get their questions on the screen for Guido’s keynote speech (took me a while to realise what was going on…).

Throughout the conference you get a mixture of the very immediate (”Has anyone got a Mac VGA Adapter for Room C?”), the impending (”BoF Session for Ruby Enthusiasts in the downstairs toilets”), the infinitely retweeted (”Unladen Swallow….”), the humorously overheard (”OH: OK; Yak shaved”), the running-joke (”Bring goat food to the Testing Sprint”), the contentious (”We were more diverse…”), the you-had-to-be-there (”Looks like @djangopony was left unattended”), the gratitude (”Thanks to everyone…”) and of course the plain exhausted (”Back home now after #pycon”).

I obviously didn’t follow everything in real time, not least because of the time difference: I do have other things to do with my time :) But it was enjoyable watching other people enjoy themselves and feeling at least a spectator to an Occasion in the Python year. Now all I’ve got to do is find time to catch up with slides, video presentations, and A Little Bit of Python.

[*] Note to pedants: seems to me that “forum” has become an English word by adoption which means that you can justifiably form its plural by adding an “s”. If I were talking about meeting places of the Ancient World I might argue for the more classical “fora”.

My great-aunt Eileen died in November 2009 at the respectable age of nearly 87. Last night, a memorial Mass was held for her at the La Retraite school in Clapham, one of the several schools in London and in Somerset where she’d been involved for many years: as a teacher, as a deputy head or head, as clerk to the governors and as a Sister at the neighbouring La Retraite community.

She was one of those many, many women and men whose lives are lived in cheerful and unnoticed service to many others. In her case, it was in the field of education; she worked in La Retraite schools in London and Somerset all her adult life. (And, indeed, was a pupil at them when younger). I only knew her as a relative; it was wonderful last night and in November at her funeral to meet many of the people who’d known her as a friend, a colleague, and a staunch support of the schools she was involved in.

In this internet age we’re used to finding important or influential people as links on the web, pages in Wikipedia and so on. Just for the sake of it, I stuck Auntie Eileen’s name into Google and found only a reference to her funeral in a parish newsletter. Yet she — and I’m sure many others whom I don’t know — have been so very important in their small communities. When not in Clapham, she lived, worked, and finally died in Burnham-on-Sea, an insignificant seaside town on the Bristol Channel eclipsed by its slightly more famous neighbour Weston-super-Mare, where she started her work as a teacher. Her congregation set up and ran a primary school in Burnham for local children and a boarding school for girls. The boarding school closed 25 years ago and became the residential care home for the elderly in which she spent her final years. She was head of the primary school for some years and many people there will have known her and will remember the crisp precision of her speech and the warmth of her welcome.

She suffered a condition for much of her later life which made walking difficult and finally impossible. But her mind was active right up until the double stroke from which she never recovered. Until the last few years of her life she was indefatigable in her habitual help of the educational communities she served. She would drive (atrociously!) enormous distances to attend governors and policy meetings, and had an acute awareness of modern employment and education legislation which often surprised people who imagined that an elderly nun would have a somewhat backwards viewpoint!

The passing of anyone is a grief to their friends and relatives. As a Catholic myself I believe, as she did, that we will meet again in the next life. But it’s arguably as important to recognise the good which so many people do in their quiet way while they’re still with us: the children they educate; the advice they give; the stand they make in defence of something they hold dear. It was wonderful to meet all Auntie Eileen’s former colleagues at the schools she helped for so long and to hear their stories of how she’d affected so many lives.

Eileen Hewlett 1922 - 2009 RIP