Category Archives: Google

I held out on using a RSS reader for more than two years. I had a little thingy built so Ping-O-Matic would use its own results and Weblogs.com to store the last updated time of every blog it saw, and then I reordered my blogroll based on that. (The original version in WordPress parsed the whole changes.xml from Weblogs.com a few times an hour. Remember when that was feasible?) Then I would go from the top of the list to the last one I remember reading, opening each in tabs, and closing as I finished. Incidentally, this kept my blogroll from withering as many do.

At some point I started begrudgingly using Bloglines in 2004, and fell in love shortly thereafter. Where I used to follow a few dozen blogs, now I could consume hundreds and its UI just made sense to me, and just got better over time. I sang its praises often in interviews, mentioning it as one of the handful of websites I used daily. Any outages or performance problems it had seemed minor to me, only reminding me of how much I appreciated the service when it was up. Bloglines search was and continues to be the cleanest in the space.

I don’t recall exactly when many of my friends started switching to Google Reader. I had tried it at its first release and was pretty unimpressed. I saw the hubabub around Gears and how Reader was the first to embrace that. I watched with envy as friends used their trends feature to see nifty data about how and when they read feeds, and use it to cull out the non-essentials, much like I used to with my blogroll.

A week ago, frustrated to no end by a bug in Bloglines telling me to reread things I already had, I decided to make the switch cold turkey. I packed my OPML file and went along to Google Reader full-time. It hasn’t been painless — the keyboard shortcuts are a little funky on dvorak — but it feels better to be on a platform that whether real or perceived feels like it has momentum. That self-fufilling X-factor in apps is one of the magic elements for me. Also as I’m adapting to the UI I feel a lot more efficient than I used to in going through things.

Finally I’ve started reducing my subscriptions, down to 346 now, and I hope to be under 200 within a month or so. I’m thinking of adopted a fixed-number, say 150, and if I want to add one I need to remove another one first so the total is always the same. (I’ve considered this for social networking sites, too.) However it’s probably focusing on the wrong metrics, unread items is more important than total feeds.

I had read a few stories about Google services being advertised above search results as a “tip” but I hadn’t realized it was this prevalent. In their position if I was trying to get more users I might do the same, but for some reason this surprised me coming from Google. (It wouldn’ from Microsoft. Hat tip: Mark.

After speaking at Yahoo earlier, I drove a few miles down the street to Google for MySQL Camp. I caught the last session of the day, by Googlers saying how they used MySQL internal to Google. (I assume for the Adwords application.) Here are the stream-of-talking notes I took. The most fascinating bits I took out of it is how they take a partitioning/sharding strategy similar (but notably different in some ways) to WordPress.com and that they use DNS to manage all load balancing, high availability, datacenter failover, etc. DNS is a pretty powerful building block.

It’s Friday, so I’m going to take a few minutes to describe the most annoying concept I see espoused by 95%+ of blogs I read, people I talk to, and friends I have. The problem is until you let go, you’ll never be able to build something truly useful to a non-trivial audience.

“Then, when someone wants to see any of the pages on your blog, those pages are created for them dynamically, on the fly.” Sounds familiar… The new Blogger doesn’t make users wait on rebuilding anymore, nice upgrade! (What happened to all those folks saying static was the only way to scale?) That and their other new features show a real respect and sensitivity to their users, the only thing missing is an exporter. Rebuilding is so 2004.

Google Strict vs Google Deprecated, where the size of the homepage is reduced using standards-compliant markup. I’m guessing this isn’t a religious issue, just a personal one with whoever owns that code at Google.