My wife and I keep a blog about our recent move to Buenos Aires. Michele is a non-stop, daily blogging machine, while I write a post, oh about once a month…which may not be a very impressive body of work, but it certainly beats my track record around here lately!

In addition to my relative lack of posts, what’s also been missing on our blog has been my Twitter updates in the sidebar. Why? Because while Twitter provides a nice, simple widget that works well for including Twitter updates on the blog, it only works for a single user.

But, what if you have a blog with two writers, and they both want to include their tweets in the sidebar? Here’s how I finally solved that problem.

What Goes Wrong When You Add Two Twitter Widgets, Anyway?

I’m no javascript expert, but Twitter’s widget code is fairly simple:

First, Twitter generates the following lines of HTML, which you paste into your blog’s template. With WordPress, it’s easiest to put it in a Text Widget in the Sidebar.

The HTML for the second widget looks like this:

Looks familiar, right? In fact, the only difference is the different Twitter user name in the second script. It’s now MichRee.json.

Notice that the <ul> in this widget has the same exact id as the first one: “twitter_update_list“. That’s where the problem lies, because watch what happens:

1. In the first Widget Text Box, toffermann.json calls twitterCallback2, which looks for the first unordered list element with an id of “twitter_update_list” in the page’s HTML, where it inserts the list of toffermann’s tweets.

2. Then, in the second Widget Text Box, MichRee.json calls the same twitterCallback2 function, which again searches for the first unordered list with an id of “twitter_update_list.” And, rather than find that list to be empty, this time it finds that toffermann’s tweets have already been inserted…so it goes ahead and overwrites them with MichRee’s tweets.

Final result: One widget displays the wrong updates, while the other widget is blank.

Oops.

My Not-So-Easy Two Step Solution

1. Change the twitterCallback2 Function

   I modified the twitterCallback2 function so that it looks for an element ID that includes the Twitter user name, not the hard-coded “twitter_update_list” ID.

   After running the blogger.js code through javascript tidy and changing just the last line of the function, it now looks like this:

   I saved the modified file as wp-includes/js/twitter-simple.js.

2. Change the HTML in the Widget Text Boxes

   Include the Twitter user name in the <ul> element ID, and then point to our newly saved twitter.js file.

   That means, in Widget Text Box #1, you put:

   And, in Widget Text Box #2:

And, that’s that! You now have updates for two Twitterers on the same page.

That Seems Complicated. Aren’t There Any Other Solutions?

Why, Yes. There are a ridiculous number of Twitter-Wordpress solutions out there. Here is a list of the main contenders I considered that can handle multiple Twitter users…and the nitpicky reasons why I ultimately rejected them:

1. Twitter for WordPress by Ricardo González.

   A strong contender. But, it’s not super configurable, so I couldn’t get the output to look exactly like the output of the Twitter widget. It can’t make the timestamp linkable. And, it doesn’t always show timestamps for tweets in “human readable format”. I prefer it to say a tweet was posted “about 4 days ago”, rather than posted on “03/22/09”, but this plugin switches to the dd/mm/yy format if the tweet is more than 24 hours old.

2. twitterjs by Remy Sharp.

   Looked promising, but since it’s not a WordPress plugin, it requires a bit more configuration than I was hoping for. Plus, it also doesn’t do “human readable format” timestamps for tweets older than 24 hours. (Though it looks like earlier versions did do it, so I wonder why it changed.)

3. Twitter Widget Pro by Aaron Campbell.

   I came very close to using this. It’s almost perfect. But, here’s where I get really picky…In addition to the text of the tweet, it also shows its “source”. (As in “this post was sent by TweetDeck.”) I know that twitter.com shows the source as well, but I think it’s superfluous information, and I don’t care to show it.

Since I’m naturally predisposed to the paralysis that comes from over-thinking, I’m always on the lookout for stories that inspire me to Just Start. Don’t worry so much about making a mistake. Don’t try to figure out optimal path. Just Do Something.

The life story of Greg Mortenson, as told in Three Cups of Tea, contains a great example.

Greg is a mountain climber who comes back from his failed summit attempt on K2 determined to build a school for a remote village in Pakistan. He has no money, next to no possessions, and no idea how to begin. For his first step, he decides to type a letter to anyone he can think of who might be willing to donate money.

He doesn’t use a computer, because he doesn’t know how. Working away on an old typewriter, he takes all day to complete his first 6 letters. All in all, he writes 580 letters.

He sends the letters to Senators, to rich people, and to various celebrities. Oprah might help, he thinks.

For all that effort, he gets only a single response (from Tom Brokaw), netting him a total of $100. A hugely unsuccessful fundraising effort.

You could argue that sending the letters was a complete waste of time, but it got him started. He took that first step towards his goal. And now, fifteen years later, his organization, Central Asia Institute has built over 60 schools that provide education to over 25,000 students throughout Pakistan and Afghanistan

Got a big project and you don’t know where to start? Type a letter to Oprah.

I’m not exactly a climber (among other reasons, I’m getting increasingly more and more afraid of heights as I get older), so how we use it in our house is a little less life-and-death:

“To get the kids to bed on time, we’ve got to eat dinner early. That’s the crux move!”

We’ve used this phrase for so long and so often, I forget it’s a bit obscure. But, recently reading about a phrase with a similar meaning made me think about it again.

The new phrase came from a profile of Lenny Dykstra in the New Yorker:

“The one-one count is another of Dykstra’s baseball metaphors for life, meant to illustrate that some moments, and the choices they bring, are more fateful than others (i.e., the next pitch makes all the difference), or, in this case, that circumstances set in motion during the early stages of development are difficult to overcome later on. If a batter falls behind, one ball and two strikes, he’s in a hole from which, the statistics augur, he will not recover, even if he is Barry Bonds; and if he gets ahead, to two balls and one strike, he wrests control from the pitcher and takes charge of his own destiny.”

Have we been using our beloved “Crux Move” for too long? Perhaps it’s time to phase it out. Should “One-One Count” be the one to replace it? Can my wife stand to hear me quote the wisdom of Lenny Dykstra on a regular basis? Time will tell…

Which means that my short-lived blog is already at a critical stage. My last post promised updates “in the next few days”, and now here it is, almost two months later, and I haven’t posted a thing.

Clearly, I’ve lost my blogging momentum.

Let’s try to pick up where I last left off and pretend like none of this happened. And, I’ll try not to lose the “Big Mo” again.

Over time, we find that some phrases fall by the wayside, but others, often the unlikeliest ones, become conversation shorthand that we use again and again.

Consider the next series of blog posts to be a phrase book, useful for decoding the strange expressions you might hear us say. Today, we’ll start with a golden oldie, then in the following days, move onto more recent additions.

Squash in the Fridge

Ten years ago, my brother-in-law overheard me call out:

“Honey! The butternut squash—do you store it on the counter or do you keep it in the fridge?”

Oh, no! Crisis!

At the time, he was in a relationship that was going through a period of high drama. What kind of a future did he and his girlfriend have? Should they even stay together? (Ultimately, they didn’t.)

The contrast between their relationship and ours was too much. Obviously, my brother-in-law concluded, my wife and I were leading a ridiculously pampered life, since the most pressing issues we had to deal with in our relationship involved the proper storage of fruits and vegetables.

So, now anytime my wife and I find ourselves nattering endlessly about some everyday minutia, and we need a reminder of just how inconsequential our argument is, one of us will stop, look at the other and say:

“It’s like squash in the fridge.”

Google Put on Quite a Show Last Week

In my last posts that focused on the developer sessions and keynotes, I didn’t really capture the overall feel of Google IO, leaving out a few key details…

Like the Food

Google is famous for pampering its employees with their gourmet fare, and they went all out to pamper their conference goers as well. Full breakfasts, numerous lunch choices (I went with the grilled skirt steak myself), and an endless sea of snacks. There was a wall of candy bins, freezers full of Haagen Dazs Ice Cream bars, and constantly replenished sodas.

And, strategically placed throughout the Moscone Center were Googly colored bean bags upon which you could plop down and enjoy the bounty.

The Evening Party

Where there was even more food. And everflowing beer and wine…and molten chocolate. (Yes, there were fountains of molten chocolate, in which you could dip your marshmallows and cakes on a stick.) But, there was more than food. Everywhere you looked: Dozens of video games. Foosball tables. Billiards. Air Hockey. Big screen Wiis.

As I overheard one conference goer describe the scene:

"It's like a sixth grader's wet dream."

Did I Mention the Band?

Now, understand that I’m old. And, I don’t have HBO. So, I’d never heard of Flight of the Conchords. (When I looked them up on YouTube, I was shocked that each of their songs had over 1 million views. What do I know?) It turns out that this “folk-comedy duo” from New Zealand is kind of a thinking man’s Spinal Tap, with a gift for deadpan, hipster patter.

Because, it wasn’t so much their songs that had me entertained, as it was their rambling stories that they interwove into the music. They told tales of traveling in time, and being locked in David Bowie’s bathroom with not one, but two Tina Turners (one from the future, naturally), and fathering tiny, imaginary children.

At least that’s what I thought as I walked back to my hotel on Wednesday night: funny shtick, funny stories, amazing delivery.

But, I was wrong. Their music made more of an impact than I first gave it credit for, because it is now 5 days later, and I still have their closing number going through my head. You know, the one where the entire audience rose from their Googly bean bags, waved their hands in the air, and sang along:

  Brown paper, white paper
  Stick it together with tape
  The tape of love
  The sticky stuff.

Marissa Mayer kicks off her speech by talking about artists and fashion designers creating custom background images to use on iGoogle home pages. This is what’s exciting at Google right now?

Minutes go by, and still more fluffy iGoogle talk. Now, I’m really worried…she’s going to crash and burn. I mean, she’s speaking at a conference for developers…and she’s talking about wallpaper?

Thankfully, once she really got going, her speech turned out to be quite entertaining and was filled with funny stories about the early days of Google.

Some tidbits:

• She once asked Sergey Brin to explain the spare design of the original Google home page:

  “We didn’t have a webmaster…and I don’t do HTML.”
  

• Early user testers would just stare at the Google home page…and not type anything into the search box.

  Why?

  They were waiting for the rest of the page to load.

  To solve this problem, Google had to add a footer, so people knew the home page was done loading.

  “Our copyright notice isn’t legally required.  It’s punctuation.”
  

• Every search query on Google hits between 700 to 1000 servers before serving the response. Think about that the next time your search results return in 0.09 seconds.

• “Design is becoming more of a science than an art.”

  They do tons of A/B Testing at Google, testing every tweak to the site on a small percentage of their users and then watching to see how it impacts their “Happiness Metrics”. Which means that they don’t have to guess which design or feature is better. They have numbers, hard evidence that one is better than another.

  Two examples:

  • Less white space around their logo made their users more satisfied.
  • Displaying more search results per query caused happiness to plummet, because adding even the tiniest fraction of a second to the page response time resulted in decreasing user satisfaction.

I’ve put myself on a self-imposed “App Engine Only” track, so I haven’t really followed the news and announcements regarding Android, or OpenSocial, or Google Gears, or any other Google initiative.

Though they did show a way cool Android mobile phone demo in the Keynote. The phone had a built-in compass, so you could run the Google Maps application and look at the Street View, and then as you moved the phone, the Street View would sync to the new compass direction. In other words, as you moved the phone from North to South, the Street View photos would also pan from the North view to the South view. Spontaneous cheering from the crowd.

App Engine Talks

In any event, here are my takeaways from today:

• Use Django. Don’t use the one that’s bundled with App Engine (v. 0.96). No, check out the latest development version of Django from subversion (currently 0.97). What’s interesting is that even though Google App Engine ships with the webapp framework and with Django 0.96, Guido van Rossum chose to devote his talk to how to install and use Django 0.97 on Google App Engine. I was curious what that meant for webapp, so I asked if there was ever a reason to use webapp instead of Django. Guido’s answer was that webapp was simple and enabled you to get started very quickly. But, Django was more powerful.

• If you use the Datastore correctly, scaling comes for free. But, it takes a lot of work to use the datastore correctly. Further complicating the issue is that nobody knows exactly what “correctly” means yet.

• Pay special attention to Datastore writes. “Reads are cheap! Writes are expensive!” Every write is a serialized transaction that hits the disk. Rule of thumb says you can’t do more than ~100 seeks/sec, so that’s the upper limit for write speed.

• For high-contention write situations (like a counter), don’t write to a single, global counter class. Instead, use “sharded writes” where you write to several entities, and then sum the totals from all the shards to get the total count.

• Entity Groups are for transactions. I did not understand the point of parent-child hierarchies for entities before today, but now I see that their only purpose is to group entities that need to be changed together as a part of a transaction.

• The Datastore will not help you maintain data integrity. It’s entirely up to you, especially when you are updating or deleting entities with ReferenceProperties. Seeing the code examples today that showed how to handle deletes properly makes me appreciate how nice it is to have a relational DB handle this automatically.

• Don’t use count(). Ever. This was stressed in several presentations. Not only can it not count past 1000, but it also requires a scan of every entity, thereby using way too much processing power.

• You can’t use JOINs in queries, but you can utilize the foreign-key-like ReferenceProperty to associate entities and therefore, do JOIN-like queries on them. In Rafe Kaplan’s talk about “Working with Google App Engine Models”, he walked through one way to model one-to-many and many-to-many relationships. I found this particularly interesting, in that it demonstrates how to have a relatively normalized data model, directly contradicting the emerging idea that the best way to take advantage of the Datastore is aggressive de-normalization.

• The index.yaml file defines the composite keys needed for complex queries. All queries rely on the Indexes, which are separate BigTable tables. If a property value isn’t indexed, it can’t be found by a query. Now, that’s not a problem for querying by kind or single property values, since indexes are created for these automatically, but it is relevant for complex queries, since composite keys are not created automatically. (The dev server automatically updates the index.yaml file as complex queries are run in the dev environment, so as long as you test every query on dev, you’ll be fine.)

Several themes came up over and over in the Q&As that followed the talks:

• Maintaining Data Integrity, Especially over Time. How do I migrate data models? How do I delete columns, or rename columns? How do I rename classes? How can I make changes and not break data integrity? Nobody’s figured out good answers to these questions yet.

• Bulk Data Operations. How can I import and export large data sets? How can I bulk delete? The App Engine team stressed that they were well aware of this limitation.

• Full-Text Search. How can I do full-text search over my data? Shockingly, developers uniformly expect Google to be really good at full-text search…imagine that! Sadly, it’s not there yet, though Google engineers mentioned that there’s “currently a hack in place that kind of works”, and that they would provide this feature sometime in the future.

In his presentation on how the Datastore works under the hood, Ryan Barrett offhandedly mentioned the three big priorities for the Google App Engine Team right now:

1. Data Import/Export
2. Additional languages
3. Billing

All in all, the Google App Engine talks were fascinating. Using Datastore is so new, and it’s such a departure from using a relational DB, that it’s exciting to see everyone try to figure out how to best utilize it. Though, one thing I was struck by was how tentative some of the suggestions were from the Google engineers. I had expected that since they have several years of experience building applications on top of BigTable, that they would have created more definitive best practices for how to handle common data models and for maintaining data integrity. Perhaps it’s so new that even Google is still figuring out how best to work with it.

Not knowing what to expect when I arrived, I quickly found an enthusiastic crowd, plentiful food (bagels stacked high and all the Bubble Tea you could drink), and lots of interesting sessions, with topics ranging from WordPress to CrossFit to Bikes to Patents to Predicting the Stock Market.

You are Your Twitter Name

As you register, you’re handed a badge so you can write your name and other key information. But, you don’t identify yourself by your email address, or your blog, or your domain name. Instead, at BarCamp Portland, your identity is your Twitter identity.

As I looked around at other people’s badges, I noticed that nearly everyone had a Twitter name.

I was surprised at how ubiquitous Twitter was. “What’s wrong with the alternatives?”, I wondered. Here’s my stab at some answers:

• Email. Too much spam. People suffer from email overload. Plus, there’s no way to learn more about someone if you have only their email address.
• Blog. Not everyone has a blog. It’s much easier to start twittering than it is to set up and maintain a blog.

Whatever the reason, Portland BarCampers have clearly chosen Twitter their default online profile.

WordPress as CMS

I sat in on several WordPress-oriented sessions, and “Using WordPress as a CMS” was my favorite. Ben Hengst from Powell’s Books talked about they were using WordPress on powells.com.

The Powell’s Web site is made up of many different systems (some written in perl, some in PHP), and WordPress currently only powers the PowellsBooks.Blog section of the site on the front-end. But, as the developers and Marketing folk began to use WordPress more and more, they found that it offered a simple interface for Marketing folk to input reusable content, and that it’s database structure could handle the different types of content they required. Ben said that using a combination of tags and categories gave them all the flexibility they needed.

So, now, they are inputting content with the WordPress Admin interface on the back-end, but then pulling that content from the WordPress database with the perl and PHP code that runs the rest of the site. In other words, much of the content that is entered in WordPress is never displayed by WordPress.

Random Observations

Sometimes it’s the little things that you see or hear about that make the event worthwhile.

• I heard the story of writing an innocent blog post about how you are unable to burp on demand…and watching a whole community of non-burpers spring up around it.
• Reid Beels was giving an overview of how to write a WordPress plugin…and then offhandedly demoed a really cool javascript photo display (hover over one photo and see how the rest of the photos evenly resize).
• I spotted someone wearing not only a Utilikilt, but Vibram Five Fingers shoes as well. A somewhat radical look…but he totally pulled it off.

These days, you don’t even have to make an effort to be on the Internet. Even without starting a blog, you’ll find that your name, or your photo, or even a video of you, will somehow make its way onto the Web.

• All you have to do is work out at a gym.

  My gym is called Crossfit HEL. (Add an ‘L’ for an even more appropriate name…) Every time I complete a “Workout of the Day” (WOD), my time or score is posted on the CrossFit HEL blog. Sometimes, my photo is even posted.

• Or, you can just take an Olympic Weightlifting class. (I’m in the back row.)

  
  

• Or, you can take a class on making strawberry jam. (I’m the only guy in the video.)

I guess nowadays, there are no offline activities. All offline activities inevitably wind up online.