Follow by Email

Friday, March 27, 2009

Twitter at EclipseCon


Well, EclipseCon is finally over. First, I'd like to thank everyone for the great job they did. I was told they put extra effort into making interesting sessions, and it showed.

Good 'ol Ian Skerrett, my favorite marketing guy, arranged for attendees to use their Twitter accounts to talk about the conference by including the #eclipsecon tag in their tweets.

I spent a couple of hours this evening calculating the number of times a user used the #eclipsecon tag. (Thanks to the Twitter Search API and Perl.) You can view the full per-person counts here, or read below for the top 20, along with a full distribution of tweets per person:

User#eclipsecon tweets
oisin148
eclipsecon146
IanSkerrett93
lorifraleigh78
njbartlett61
douggaff49
alblue49
peterfriese48
motodev47
darinrs46
michael_scharf41
waynebeaton40
irbull39
rfarrjr37
jplmichael36
jeffreynorris34
BryanHunt34
ericcloninger33
vineetsinha32



I was just below this list at #21, with 31 tweets. (Actually, just 30, but I'm going to tweet about this too, so I fudged.)

See ya next year.

Update: I should have commented on the word cloud. I find it super interesting. I only removed four or five phrases (the ones that come to mind are eclipsecon, http, tinyurl and com) and if you look past some of the common English words (demo, day, thanks, rt -- should have removed 'rt') there are those technologies and phrases that seemed to get the most traction: rcp, e4, amazon, p2, cocoa, glassfish, equinox, and my favorite: @ianskerrett.

Monday, March 23, 2009

To non-techie friends on twitter and the facebook: Sorry about this week

Hey there: this week is EclipseCon. It's a technical conference in Santa Clara revolving around the software tool called Eclipse. So, most of my tweets are going to be about EclipseCon, at least until Thursday. (These tweets wind up as status updates on The Facebook.) So, sorry about that.

If you're on The Facebook, you probably wonder why my status messages say "#eclipsecon". Well, that's basically a meta-tag indicating what my message is about. Then, people who want to know what's going on at EclispeCon, they can just look at the realtime results at http://search.twitter.com/search?q=%23eclipsecon. (Interested in Battlestar Galactica? Search for #bsg. Same goes for #lost, or #chicken, or whatever.)

So, you know, I kinda likes the Twitter. You should try it, and if you do, we can follow each other.

Sunday, March 08, 2009

Saturday night with Uncle Floyd

Last night, Beth and I went to see Uncle Floyd perform at the Maplewood Public Library. The last time I saw a New Jersey legend perform at a local library was when I went to see John Pizzarelli at the Mamaroneck Library in 1994.

With the exception of occasionally seeing Uncle Floyd on his TV show, I didn't know what to expect. Though it was a small crowd of 25 people, Uncle Floyd was shockingly funny. It's clear he's done the same jokes for many, many years ("I'm the only working comedian left with a Bella Abzug joke.") and yet he was solidly funny. It's also a bit of a retrospective into yesteryear, with jokes about old-style remote control-free TVs, and Alfalfa and the Little Rascals.  Some cultural jokes were too early for me, and there were jokes that people younger than me would certainly not get.

Aided by his trademark plaid outfit and bow tie, Floyd was shamelessly self-deprecating, lamenting that after forty one years in show business he finally made it to the basement of the Maplewood Library.

For ninety minutes we all had a great time.


Wednesday, March 04, 2009

License To Recite Fox in Socks

Do you have one of these? Mine is almost fifteen years old.



Only three of these were ever made. I will buy anyone chocolate who can tell me who received the other two (limited to the first ten correct guesses.) I will add ice cream to that if they can also tell me who the fourth person was. And if you're one of those people, do you still have it?

Sunday, March 01, 2009

Building a National Pet Identification System in Java

This week I dealt with a rather irritating little problem that wound up having a surprising source. Rather than try to explain it to my wife in technical terms, I went for the more prosaic form, but for those of you that are familiar with Java, it's all about this.



Congratulations! President Obama created a new Cabinet post, and you became the first Secretary of Pets! Your first task: managing and categorizing every pet in the United States: dogs, cats, budgies, snakes, it's your domain. You decide to identify every pet by giving them a unique nationally-assigned number. References to that number are the same as references to the pet and references to the pet are the same as references to the pet's identifying number. You create a huge central station just outside Lebanon, Kansas and process requests as they come in. Someone requests an identifying number for a Maltese cat in Michigan, they get 104558628. The next request is for a wire-haired terrier in Pasadena, CA and they get the next one: 104558629.

You've also been tasked with creating an abstract broad classification system. It's an odd classification requirement: you don't need to classify by species, number of paws, color, gender, geography or fangs, just something that lets you batch them up. So you create a classification based on the identifying number already given to the animals by declaring an animal's classification as the last two digits of the identifying number. So if your wire-haired terrier's identifying number is 104558629, its classification is 29.

So far so good, your central station is humming away, doling out identification numbers. One day your sister's cat goes missing, and she goes to the Lost Pet Center. She doesn't describe the cat, she just gives her cat's identification number 104558628, and a Lost Animal Ticket is stored in the National Lost Pet Database.

Remember when I said earlier that referencing a pet is virtually the same as referencing a pet by its identification number? Thanks to this you were able to build a Pet Identification Station in every town: put the animal up to a station scanner and, presto! It displays the animal's identification number.

Also in every town is a Lost Pet station. It's awesome: if you find an animal you don't even have to bring it to the station, you just supply its identification number. When you do, cogs turn, phones dial and the Lost Pet station connects to the National Lost Pet Database, and asks it: "Is this identification number in your Database?" If the response is no then it's not a lost pet, and if the answer is yes the cogs turn and phones dial. The Correct Authorities are notified and before you know it, your sister's cat is safely returned. In fact, she just told me so about an hour ago, and her cat's making all sorts of happy purrs. Do you like happy endings? I love 'em.

I bet you're a little sad that there's a National Lost Pet Database. Don't be sad - it's not a terribly large list, and it's certainly smaller than before you ever built your pet identification system.

But it's large enough that everyone wants it to respond as quick as possible. Nobody wants the National Lost Pet Database to be the source of delaying a pet returning to its home, particularly not the politicians, at least, not the savvy ones. But right now, how it works is like this: every entry in the database is a Lost Animal Ticket. The Lost Animal Ticket contains the identifying number of the pet as well as a piece of information about the owner to facilitate fast contact. When trying to decide if any pet is missing given its identification number, the system creates a prototype Lost Animal Ticket, and attempt to match the prototype ticket against every entry in the lost pet database. If the identifying number of the first entry matches the identifying number on the prototype ticket, it's considered a match. If not, it moves to the second Lost Animal Ticket entry in the database, and performs the same test. This repeats until a match is found or until the entire database is exhausted. It's a bit like trying to find a playing card in a deck by taking a prototype card from yet another deck and attempting to match it against the first deck through visual inspection.

So to make it faster, you come up with a Great Idea: split the database into several miniature databases. In fact, thanks to the classification system you designed, you can just split the database into a hundred mini databases, and in each mini database you only put Lost Animal Tickets for pets with the same classification number. So now you have one mini database for all Lost Animal Tickets for pets classified as '00', one for all pets classified as '01', one for all pets classified as '02', and so on up to '99'. This really works well because every mini database is about as large as every other, and even better, instead of search through every Lost Animal Ticket, you just search one of the mini databases in 1% of the time. Instead of searching through all the possible missing pets, you only have to search through the mini database for pets classified as '28', which as we know are the last two digits of your sister's cat's identifying number. In some ways this is like trying to quickly search a deck of cards by separating them based on their suit first.




All of this works and is predicated on three important things which may seem obvious: first, everything that tries to classify a pet must consistently perform the same step to get the classification number, which is to create a Lost Animal Ticket, read the identification number from it and use its last two digits; second, that whenever attempting to match one Lost Animal Ticket against another, this must be performed by matching the identification number on each of the two tickets; and third, those first two things agree that the identification number is what matters.

And here's the thing: what happens if any of those assumptions are wrong? For instance: one day you decide to categorize pets by the first two digits of the animal's identification number instead of the last. While your sister's cat's Lost Animal Ticket is sitting in mini database '29', everyone may look in mini database '10'. All of a sudden nobody can find your cat, or it's registered in two separate mini databases.

Here's something else that can go wrong: instead of comparing Lost Animal Tickets using the identification number of the animal, the system uses the identification number of the pet's owner. If your sister lost three cats and one is found, it's quite possible for the wrong ticketto be matched against the prototype ticket. Also consider instead a possibility where the criteria for deciding if tickets matched changed to being the same physical piece of paper. Doesn't make sense? If you and I both have a four of clubs, we could possibly agree they were the same card. (That's basically how the National Lost Pet Database works.) But if instead of playing cards, we had airline boarding passes, it would be safe to assume that if you were standing on an airplane with our own boarding passes, if they referred to the same ticket, someone may call The Correct Authorities, and if we applied that algorithm to the National Lost Pet Database, then pets would practically never be found.

Finally, your system will fail from a poor combination of the first two requirements: if your system's categorization calculation is inconsistent with its test for equality, the system may lose tickets. For example, while the first example of possible failure still used the pet's identifying number, what if classification was something more arbitrary, like the time the ticket was issued? The prototype ticket will have been issued at a different time from the lost pet ticket, and as such will likely be classified in different mini databases, and never be found, or only found due to something repeating the same error (Like the time nobody at the bank could locate my account until someone mistyped my name the same way as the teller who registered it on my behalf. That's another story.)

Luckily for your sister, you didn't make these mistakes. Your National Pet Identification System is a huge success, and President Obama has now tapped you to address the problems with our banking system, just like Moist Von Lipwig.

Keep in mind: if anyone plans to write a National Pet Identification System in Java, read Items 8 and 9 of this book. You may save someone both several hours of work and their wire-haired terrier.