Category Archives: i am a nerd

Toyoko INN for railfans

Looking to stay at a quality business hotel, but don’t want to tear yourself away from the trains? Look no further: Toyoko INN delivers!

That’s right… From certain floors and rooms of the Toyoko INN chain of hotels, you can overdose on train watching without leaving the comfort of your bed. Just ask at the front desk to be accommodated. Here are some samples of train views from their various hotels, including the one I’m going to be staying in next week!

Screen Shot 2013-04-04 at 5.55.49 PM

Not only do I get to enjoy Sendai and the hospitality of Tohoku University, but I’ll potentially get some great views of the Tohoku Shinkansen while I’m there. I thought Toyoko INN outdid itself when I received socks and q-tips as “presents” when I became a point club member a few years back, but I was wrong. Can’t wait!

 

why print?

I recently uploaded a new (and my first) resource to my site, a guide to print reference resources for Japanese humanities held by the University of Michigan. This guide was originally made for a reference class in 2008, so it’s about time that it saw the light of day. It certainly wasn’t doing much good sitting on my hard drive.

You might ask, though, on viewing this: Why would Molly make a resource guide for only print books? Aren’t they a little, well, archaic and outdated? Isn’t it more convenient to check out digital resources from the comfort of my own laptop, perhaps in bed? After all, there are fantastic reference resources – available through institutional subscription – such as the JapanKnowledge database that suit many needs, and bring together information from a wide variety of (originally) print sources and other databases. With something like JapanKnowledge, going to the Asia Library Reference Room and thumbing through dictionaries seems a little slow and pointless.

Let me tell you something. In the process of looking at the various humanities reference resources, for literature in particular, I found a large number of unique sources that aren’t available online. These range from the legendary Morohashi Dai kanwa jiten Chinese character dictionary to synopses and reception histories, guides to folk literature, a multi-lingual proverb dictionary (it has translations and annotations in Japanese, English, French, and German), and a guide to Buddhist terms found in Japanese literature that include the original Sanskrit and phrases from the classic literary works containing the terms.

Among the books that are entirely unique – an equivalent resource doesn’t exist in any other format (or, sometimes, language) – are a biographical dictionary of foreigners in Japan from the 1500s-1924, an annotated bibliography of translations into European languages dating from 1593-1912, an annotated bibliography of Japanese secondary sources on literary history published between 1955-1982, poetry indexes, and a dictionary of popular literature (taishū bungaku).

The process of making this bibliography was the pure joy of a scavenger hunt, and did I ever come up with a list of treasures. Leafing through a book of English-language synopses of untranslated Japanese work from the 19th-20th centuries may not sound exciting, but the fact that it exists as a quick reference resource for those looking to read some Meiji or Taishō literature is pretty amazing. I had a good time in the Reference Room finding these resources, and I’ve put some of them to very good use over the years.

Yes, I use digital resources; in fact, I couldn’t have come up with my dissertation topic without them. (As always, many thanks to the National Diet Library for the existence of the Kindai Digital Library.) But Japan is still a world of print – it’s nigh impossible to get a journal article in electronic form at this point – and, more importantly, print reference sources like these don’t go out of style. A guide to poetic allusions from the 1950s, or a popular literature dictionary from 1967, do not become outdated or irrelevant; we may wish for an update to the latter, but the information it provides is still valuable. Being able to use print reference works opens up a world of information to us by supplying that which has not been converted to database form.

Finally, why this guide? Is a guide coming for electronic resources? The short answer is, save for one-off blog posts, no. There are already so many excellent guides to electronic resources out there on the Web that my own meager contribution wouldn’t make much of a difference. The reason for this guide is that I haven’t found a good annotated bibliography of print reference books for Japanese literature specifically, and humanities more generally, that live at what used to be my own institution. I wanted to both know for myself, and share with others, what treasures were hiding on those rarely-used shelves (and, worse, in the off-site book storage) – what treasures were at my fingertips.

I hope you find it useful, and if you’re at the University of Michigan – or hey, anywhere else, for I can always check the catalog – and you have your own preferred humanities reference works, please send them along or leave the info in the comments. This is an evolving work and I’d like to include everything I possibly can!

android slashdot reader: 和英コメントで言語学び!

Now that I have an Android phone and have found some pretty great things on the Android Market for getting ahold of Japanese content, I would like to start sharing with you all what I’ve been using and whether it’s worth downloading.

First up is my favorite new find: Slashdot Reader. Yeah. It’s an RSS feed reader for Slashdot. Why so great?

Well, can you imagine my reaction when I read its description and saw images of posts from slashdot.org and slashdot.jp showing up all mixed in together? Then I read the description: “just a feed reader, nothing more” – for both Japanese and English Slashdot.

It’s like I found an app made by my doppelganger. Really.

If you don’t want one or the other of the languages, it allows you to toggle both, Japanese only, and English only.

Because it’s a feed reader, you only get the headlines and leads from Slashdot, but can easily click through to the full story, and therein lies the amazing language learning tool that somehow never really occurred to me.

All of these years, I could have been learning Japanese through Slashdot comments! That’s right. Of course it’s not textbook Japanese. I already know how trolls (荒らし) talk after just a minute or two of reading. How nerds talk. (They always use が and never けど, although they do use ね sparingly for emphasis. A certain language teacher from several years ago who forbid us from using けど in class for an entire semester would be proud.) And how random users talk.

I also know how they’re basically saying exactly the same things that commenters do on Slashdot in English, only they’re saying it in Japanese. (open source != free as in beer, anyone? I seriously just read this. 無償 is free as in beer, and note that it’s not the same as the widely-used word for “free” 無料 – so I just learned something new about software licensing.) So if you’re a Slashdot reader, this is going to help you immensely. It’s all about context.

Yes, so there are people out there who would disparage the idea of learning language from internet comments. But I counter that with: it’s real language! And this is a specific forum where you know what is coming: some nerdspeak, some posturing, some trolls, some reasonable people, talking about a rather limited set of topics. So you are going to learn voices, not just “Japanese.” You are going to learn what people say in a certain situation, and also what not to say. I can’t think of anything more helpful than that!

And here you go: Slashdot Reader for Android (this takes you to Android Market).

Showa 40s vs 1970

I was listening to a podcast interview with a favorite author just now (Kakuta Mitsuyo if you’re wondering) and I came to a realization about Japanese and Western calendars. From Meiji onward, I have come to crave dates in Japanese reign years when using Japanese, crazy as it sounds – I want to ditch Western years altogether!

Why is this? Frankly, Western years take a mouthful to say and are much harder to pick up when you’re listening, especially if the speaker is talking quickly. 2009 becomes “the year two thousand nine.” Try 1999: “the year one thousand nine hundred ninety-nine!” Do you see the problem?

Well, many learners of Japanese hate the confusion of having a separate, less often used Japanese reckoning of years according to emperors’ reigns. The infamous Hirohito is known as the Showa emperor in Japan and the Showa period starts with his coronation in 1926. I was born in Showa 56 – 1981. Incidentally I know this because the high school where I taught my first year in Japan functioned on Japanese years and one needs to know one’s birthday! For most official forms, you are still expected to write your birthday in Japanese years. If you want to impress a functionary, learn this and write it proudly. They will be unnecessarily astounded.

In any case, the author was talking about her childhood and said “In the Showa 40s…” I actually sighed with relief! When the host breezed over that day’s date in Western years at the beginning of the podcast I had simply stopped listening, but Showa 40s – it just clicked. 1965-1975. It just makes sense to me somehow.

As you may know, I study the Meiji period (1868-1912). Specifically, it’s the Meiji 20s, or 1887-1897. I find myself writing dates as Meiji 20-something all the time. Why? I can’t explain it. It’s certainly in part because publication dates in the books I read are all in Meiji years – it was still the norm then to use Japanese years. But I can convert easily now from studying it for so long. So, why?

Really, it’s not me becoming accustomed to Japan. No normal Japanese person born after the Taisho period (1912-1926) would do such a thing. I think it’s much simpler: I am a nerd who studies literary history. It’s the sad truth. Well, a happy Heisei 23 to you all then!

(By the way, why no pre-Meiji reign years for me? They’re too short, numerous, and confusing. They sound the same. I just can’t take it. But if I studied early modern? I bet I’d be using Bunka-Bunsei like it’s 1821!)

new phone destroys old phone

I’m jumping headfirst into the 21st century here for once, rather than being dragged kicking and screaming. Yes, I have replaced an old electronic device (to be fair, only 1.5 years old) with a fancy shiny new one.

Samsung Epic 4G

I posted once about my Blackberry destroying certain parts of my internet life by being a laptop replacement that nonetheless can do fewer things. Well, I now have a laptop replacement that can do quite a few more things, but with a harder to use keyboard, and which sucks its battery down like you wouldn’t believe. Goodbye, poor Blackberry. I who defended you so stubbornly am now transferring your pictures away and will soon recycle you, and remember you fondly in spirit.

Blackberry Curve Purple

 

RIP Blackberry Curve Purple!

P.S. The new phone is one that someone else gave up for an iPhone and donated to yours truly. So I’m still in character, fear not.

google dropping app support; molly has PPC angst

A decision I made over five years ago has ended up making me quite unlucky these days.

iBook G4 photo

I intentionally bought a PowerPC Mac, the iBook G4, when my iBook G3 succumbed to the infamous logic board defect a year or so after Apple stopped fixing it for free. My first winter semester at Michigan had just started, so I was stuck: I needed the data from my G3’s hard drive even more than I needed a computer, and I knew that Apple would soon drop PowerPC in favor of Intel. Like the idealist I can be, I went for the PowerPC instead of waiting a while for the new hardware, because after taking some computer architecture courses and having done a little assembly programming, I had come to the conclusion that RISC architecture is superior to CISC – meaning that I favored PowerPC over Intel.

Little did I know how ghettoized the PowerPC is out there in the real world. Naive, I had no idea that most operating systems and software are not ported to PowerPC – not even Linux.** In the first few years this wasn’t a problem and wasn’t anything I noticed beyond having a matte screen instead of a shiny one. I still love my G4, with its plucky reliability and long battery life.

Starting about last year, however, more and more software makers dropped PowerPC completely, as OS X only went up to version 10.4.x on PowerPC and many required 10.5, which is Intel-only. Even the software that is still released for 10.4 stopped supporting my laptop, including OpenOffice.***

I resigned myself to having a laptop that is circa 2009 in terms of what it runs. I am okay with running a Japanese version of OpenOffice 3 that will open .docx files for me, and running Adobe CS3 and Word 2004. Honestly, I don’t need the newer versions of these programs for a base model iBook that only has 40GB of hard drive space. What I need is the reliability, toughness, and 5 hour battery life (with the ability to buy new batteries) that my 5 year old friend provides. I have a desktop for everything else!

I have a sinking feeling about it now, though. We have a problem. Google is going to gradually drop support for older browsers, which includes pretty much every browser that I can download for my PPC Mac. While I applaud their strict use of HTML5 (I use it too!) and refusal to cater to legacy browsers that don’t understand it, I realize that I am basically screwed. And how much I rely on Google, frankly.

Here are things I would like to use a laptop for: Web browsing, Gmail, Google Docs, a little word processing, PDF reading and editing, writing, and possibly a little Photoshop. And some Twitter. If I suddenly can’t access or use Gmail or Google Docs, that is a huge blow to using my laptop to be productive – it’s the point of carrying something around that will let me access my files remotely to begin with!

“Get a MacBook,” a voice pleads in my head. They are so shiny, fast, small, and nice. They’re still only 13″ but have a wide screen that makes it seem so much bigger than the 12″ iBook. They have long battery life. I’m kind of in love with them despite myself. Admittedly, I resent the non-removable battery that will allegedly last for the average life of a laptop. But if I wasn’t suddenly losing all software support for my peculiar architecture, I wouldn’t even consider a new laptop.

I just bought the laptop a new battery. It has 5 hours of battery life, does everything I need it to, and is very hardy. It’s relatively small, light, and convenient. It has some very expensive software on it. Most importantly, it simply still works fine and has nothing wrong with it. I abhor wasting things. I am fond of this laptop. If it weren’t for the uncertain nature of old hard drives and impossibility of replacing that without breaking the case, I’d argue that it probably has many years of good life left in it. It’s the Volvo of laptops.

So even if I bought a new laptop (which I can’t exactly afford now), I’d want to keep using the iBook for as long as I can. Why waste it? But why have two laptops, one running Linux?^ (Seriously, I already have a netbook running Linux.) They’re the same size. It makes no sense to keep the iBook around for anything other than preserving my installation of many pieces of CS3. And because I heart the damn thing.

I’m at a crossroads: my PPC laptop is soon not going to just be dated, but unsupported. I don’t want to waste a perfectly wonderful laptop that has seen me through an entire PhD program. I have good software on it. Why buy a laptop the exact same size and type? Because it will save me from Google no longer supporting my laptop, and Web browsers that are actually implementing new W3C standards from not running on it.

Lesson learned: Even though I want superior architecture and don’t jump at trends (like oh, x86?) that I think are not worth it, I have to just go with the crowd, because sooner or later it will leave me behind. I am still not getting an iPad though. How long do you think I can scorn touch screens before I become officially old?

* (Yes, that is how old the G3 was. About three and a half years. Not bad for a laptop with a manufacturing defect that I was very hard on.)
** There are a number of PPC Linux distributions, but specific software may or may not be ported. Usually not.
*** Weirdly, there are a few local language versions of OpenOffice that do still support PowerPC architecture. Since one of those is the Japanese-language version, I now happily use a Japanese word processor and try to keep my language skills current, at least in terms of menu choices.
^ If I could get it to run for the newest AmigaOS I would run to it without hesitation, but I have only gotten reports of it running on a Mac Mini. Don’t think I haven’t considered getting a Mac Mini solely for this purpose. The lack of a monitor is mostly what’s stopping me.

and thinking about object-oriented programming

I may be enamored with functional programming right now, but I do remember that the first languages I really learned were C and C++. That ++ is one big difference. I was fortunate enough to be learning them at exactly the same time, and so “object oriented programming” meant a lot more to me than a buzzword.

I’ll share another link tonight, and this one is more of a read, but it’s an opportunity to ask something you don’t every day: how does object oriented programming work, and how is it implemented? For example, in ANSI-C?

Object-Oriented Programming with ANSI-C (Axel-Tobias Schreiner, English translation, PDF)

thinking in functional programming

My internship this summer gives me the opportunity to get acquainted with and even use some XSLT – misleadingly the “stylesheets” of XML.

XSLT has been hard to wrap my head around, not least because “stylesheets” and “used to format XML” make me think of CSS, not – well, functional programming. It’s been a good many years since I got to play around in Lisp, let alone make something with it, and this has brought me back to those two great semesters of AI electives that introduced me to this way of thinking. It took a few weeks to get into it, but once I “got” how Lisp worked at a more intuitive level, I remember my impression: I am thinking in a different way. It wasn’t just about programming, it was about problem solving, and about a way of looking at the world.

Diving into a functional programming language again has got me thinking about that experience. Learning how XSLT works has of course made me remember a time when Lisp made sense, because XSLT is functional programming. If I had been introduced to it in that way at the outset, it would have clicked much sooner. Now it makes me yearn a little for the time when I didn’t just know that I was working in a different way, but when that way came to make sense and I was able to start going somewhere with it.

But when I learned Lisp in the context of an AI (artificial intelligence) class, I didn’t learn it as “functional programming” then either. I wasn’t introduced to it in the context of lambda calculus, which I came to find much later – last semester – in a natural language processing course. I knew it was different, but I didn’t know how on a bigger picture level.

Now that I have that bigger picture, I am appreciating this way of thinking more and more.

Why is functional programming “hard”? Why is it something that I had to get used to for a time before it clicked? I have an answer this time – because I have been doing imperative programming for so long, because that’s how I was introduced to programming (I didn’t attend MIT after all), and because that has become the natural and intuitive way for me to solve a problem. But imperative programming isn’t a more natural way of thinking about things. It’s a different way. Obviously, these two ways of approaching problems have different applications, but the elegant and concise ways of approaching problems that functional programming offers are perhaps even more appealing to me now.

Because I am not an expert, I write this not to make a profound statement about how to approach problem solving, but to share a great article about where functional programming came from, why it’s so appealing, and the things it makes possible. I give you,

“Functional Programming For the Rest of Us.”

Take the 10 minutes to read this and enjoy!

A Creative Endeavor

… or How I Will Drive Myself Slowly Over the Edge

So people talk about there being some kind of nuanced difference between nerd, geek, and dork. I’ve been sucked into it myself, sadly, and as a result I get a little defensive when I am called anything other than a nerd. By any criteria, I really am, and was way before it became ironic-cool to wear thick plastic glasses. (Just check out my fourth grade yearbook.)

I think my own personal nuance is the difference between dork (no social skills), geek (geeking out over things, becoming obsessed with things), and nerd (likes learning for its own sake and often enjoys academics as a hobby, leading to social ostracism and a joy of doing homework). Well, of course all of these things overlap in any person, but the traits of the last manifest quite clearly in me, for better or worse.

Case in point?

This summer I’m working at an internship in Lincoln, Nebraska, and had to pack one car and go (with all of my cat’s things too, so I lost some space). No bringing my ever-expanding book collection with me. I got a Kindle to read Gutenberg.org books on, but still, it would be nice to have some kind of summer project that isn’t a work assignment. A dual degree will do that to you: any kind of scheduled free time becomes exciting and a chance to either take on something with a limited deadline and feel satisfied, or lay around and do a lot of nothing. I try to do both.

So here is my project. I picked up a copy of Seven Languages in Seven Weeks and decided to work through it in the evenings after work. Yes. I am giving myself seven weeks of programming assignments. I’m going to be learning entirely new languages, some I have heard of and some I haven’t. I get a little cheating on one because I am semi-comfortable in Lisp. Still. I will learn a little of each: Ruby, Io, Prolog, Scala, Erlang, Haskell, and Clojure. I am excited about the prospect and not only do I want to learn because it’s fun and programming is fun for the brain (when it’s not hurting your brain, and when you’re not banging your head on the desk) – but also because I think it will be good for my creativity.

After all, creativity is not limited to one domain. Practicing writing helps me think more freely about photography, keeping a journal helps every aspect of my life, keeping daily notes about my dissertation inspires me to reexamine my artistic life (it helps that I write about authors and practices of writing). And there is something about exercising the brain with logic and problem-solving that is refreshing and at least interesting, and often rewarding, after you (I) spend almost all of my work life reading, and writing about stuff I read. Making art is one kind of problem-solving; programming is another.

Both are all about creativity and stretching the brain a little bit further.

But yes, it is seven weeks of daily programming in a set of languages I haven’t used before. I just taught myself Java in three days and then wrote a non-trivial application in it for a class project, and I’m somewhat exhausted. For my internship, my life is going to be all about getting better with XML and TEI, and then learning how to fit XSLT and XPath into the picture, while working with a servlet, which I have never even had to consider before. Good god, I am all about the computer this summer. It’s great.

I’ll have to stop the extracurricular programming if I feel a nervous breakdown coming on. Until then, onward to Prolog!