Retiring Python

James Hague is retiring Python as his preferred language for teaching programming. His reasoning is that so many of his students would like to be able to show friends and family the results of their efforts but that getting graphical results from Python is, well, circuitous quite often. The language with which he now wants to start beginners is Javascript.

File this under hmmmm.

Margaret Mead’s Network of Influences

As Yung-Hsing Wu continues to explore the various relationships between reading, culture, and institutional efforts to define the relationship between reading and culture (and thus human nature as well), I find myself recalling various moments in the history of anthropology or folklore studies that might be of interest to her.

One such moment was Margaret Mead’s involvement in the National Research Council’s Committee on Food Habits. The NRC had previously funded research into the “national character” of the United States, I believe — someone had, if not the NRC, and I’m not sure if Mead was involved at all. Mead’s involvement in the foodways research is summed up by the Library of Congress’ online exhibit as:

At the request of Ruth Benedict, Margaret Mead came to Washington, D.C., early in 1942, to assume the role of Executive Secretary of the National Research Council’s Committee on Food Habits. One aspect of the committee’s work dealt with determining what foods were essential to the cultural habits of people from different national backgrounds. Among other things, ensuring that people had access to the foods most meaningful to them was important to maintaining morale. This document from 1942 summarizes some of the committee’s findings on the value of particular foods to different national groups.

The online exhibit also has digitized and published online a number of documents drawn from the archives of Mead’s papers, the most fascinating of which, to me, was this diagram that Mead both typed and then drew of the influences on her own thinking and work:

Margaret Mead's Network of Influences as traced by her own hand.

Margaret Mead’s Network of Influences as traced by her own hand.

Please check out the exhibit for yourself. The Library of Congress deserves our support, and I would not be surprised if the number of online visitors they receive is one way by which they measure their success.

Stanford Dependencies in Python

David McClosky wrote to the Corpora List with the following news:

I’m happy to announce two new Python packages for parsing to Stanford Dependencies. The first is PyStanfordDependencies https://github.com/dmcc/PyStanfordDependencies which is a Python interface for converting Penn Treebank trees to Stanford Dependencies. It is designed to be easy to install and run (by default, it will download and use the latest version of Stanford Dependencies for you):

import StanfordDependencies
sd = StanfordDependencies.get_instance(version='3.4.1')
sent = sd.convert_tree('(S1 (NP (DT some) (JJ blue) (NN moose)))')
print sent.as_asciitree()
moose [root]
 +-- some [det]
 +-- blue [amod]

PyStanfordDependencies also includes a basic library for reading, manipulating, and producing CoNLL-X style dependency trees.

The second package is an updated version of bllipparser https://github.com/BLLIP/bllip-parser (better known as the Charniak-Johnson reranking parser). bllipparser gives you access to the parser and reranker from Python. The most recent update integrates bllipparser with PyStanfordDependencies allowing you parse straight from text to Stanford Dependencies. It also adds tools for reading and manipulating Penn Treebank trees.

More information is available in the READMEs. Feedback, bug reports, feature requests are welcomed (please use the GitHub issue trackers for the latter two).

Virtual VIM

I love my Mac, but there are times, when everyone is going on and on about the how tablets and smartphones are the future of computing, when I worry that I may one day have to give up my beautiful Mac interface and run a CLI box. For those days, and for those days when I need to do some work within the terminal, I appreciate refreshing my VI skills.

Thinking through Personal Data

There are, when you think about it, at least a few different categories for what is often called personal data. There is, perhaps first, the stuff you need to have with you at all times, which can be various, but usually includes:

  1. contacts, calendars, and tasks
  2. email and messages

These are the basic pieces of data that lie behind most communication infrastructures: people with whom I need, or want, to talk; things I need to get done; how my time is allotted and spent. In terms of their appearance in my life life, these are things I use, or think I use, constantly.

Inevitably, of course, there is a huge swathe of material that we would also like to have with us or at least readily accessible. I use swathe here purposefully to indicate that not only is there a reasonable amount of material but that it comes in a variety of categories, and how you handle those categories is, in fact, the focus of a large number of life-hacking and productivity-consulting websites and businesses. A lot of this stuff is, especially for professionals, electronic versions of what was once paper:

  1. documents, clippings, spreadsheets, drawings, images, etc.
  2. blended versions that new media offers us — presentations with embedded media, links to websites, etc.

However you keep it, and keep track of it, what matters is that you need it and you need it ready-to hand. In terms of how these things matter in my life, these are things to which I need access regularly.

Pushing a little further away from being central to us every day are the kinds of materials that once lived in filing cabinets, photo albums, and boxes of various sizes in closets and attics — i.e., storage spaces:

  1. materials not currently in use but have potential future use — this includes a wide variety of materials including proposals that have been submitted, plans and designs, media produced as stock, etc.
  2. materials that must be kept as records, either for personal or institutional reasons.

The long tail makes its appearance in our lives, and it reveals things that it is increasingly easy, and inexpensive, to hold onto for long periods of time, because we use them intermittently.

In temporal terms, then, we have materials that are constant, regular, and/or intermittent. And some of this bears out in terms of the services we use to maintain their existence: as a Mac and iPhone user, I’m fairly happy to let Apple’s iCloud help me manage my constant data. Apple’s 5GB allotment is room enough. For the slightly larger amount of stuff that is my regular data, I use DropBox, where my years of use have allowed me to grow my $10 for 10 gig allotment to something like 17GB. (Thank you DropBox!) But, like a lot of people, I struggle with storing the intermittent data. Right now, it sits in external hard drives either connected to a machine on my home network or sitting in one of those storage spaces away from everything else because, well, backup is important.

Data Store Size and Frequency of Access

Data Store Size and Frequency of Access

I will confess, however, that this arrangement is not as organized as I like. Yes, I keep some stuff Dropbox, not because it belongs there in terms of usage but because I can. Moreover, and running along a different axis than usage, I have some data that I would prefer to use more regularly, but because it is large in size, it tends to sit on those external drives at home. If you’re like me, then that’s stuff like your media library, e.g. iTunes in my case; my Lightroom library of images and (some video); and that catch-all collection of folders of audio, video, and images that haven’t made their way into some sort of management system or, like raw video of my daughter from when she was young, remain somewhat un-manageable, both in terms of file size but also in terms of software — does anyone really use iMovie to manage all the raw footage of their lives? (And is footage as skeuomorphic as it sounds or is it a sufficiently terminological word at this point?)

Right now, I live at the unfortunate convergence of usage and size: there are materials to which I would like to have easier access, like my Lightroom library, but I have not yet figured out a smoothly connected system. I am fairly sure from what I read that I can place Lightroom’s library on a NAS device, the same as I can iTune’s library. I don’t mind them being only available at home, so long as they are reliably accessible and the access is not dreadfully slow. This was not the case with my previous NAS device, so I’m looking to upgrade. (And I’ll happily take suggestions!)

I know there are solutions out there that offer to store all your data, or at least some dimension of the big stuff, like Flickr and Amazon now do for photography and Apple now does for music, in a way, with iTunes Match. And that’s just the free and/or cheap options. I know it’s also possible with some of the backup solutions to access materials away from home, and I don’t mind paying for that option, except that a number of them require that everything exist originally on one machine on one drive, but I don’t have any terabyte drive-equipped machines. At home, everything is a laptop or an iOS device, save the Mini in our kitchen, with rather small SSDs. That’s what has us in this pickle in the first place!

I guess I am like a lot of people, then, wanting both centrality so that I know everything is at least in one place, which also would make it easier to back up, but that I want that center to be easily accessed from the many margins of my life.