Recent Posts - Page 26

New Business Card

September 11, 2006

Figured that I might as well follow in the footsteps of Luke Redpath and show you my new business cards.

New business
cards

Our Creative Direcrtor, Allison Beckwith felt that it was time for a redesign. I should try to snap a shot of all the past PLANET ARGON cards. We have them up on a wall in chronological order… dating back four years ago this month.

Since we were doing double-sided this time I wanted to be sure that there was enough space for writing on the back… which helps with writing down a note, giving someone a coupon code for hosting, or my cell phone number if they are special enough. :-)

Meeting up in London

September 11, 2006

I’m leaving for London tomorrow. Thank you all for your responses to my travel security questions. I really appreciate it. :-)

I’m going to be getting in on Wednesday afternoon and am going to try to meet up with people at PizzaOnRails.

Thurs-Fri is RailsConf fun… but I haven’t figured out what I will be doing over the weekend. I’m leaving for New York on Tuesday.

Does anybody know of any good vegetarian places that I should go out of my way to try in London? Interested in hanging out and talking shop? Email me! :-)

Question: Travel Restrictions

September 10, 2006

Travel restrictions?

When I purchased my tickets for my trip to London for RailsConf Europe through travelocity.com, it showed me the following warning (after I paid).

Traveling in the UK:

  • If you are traveling within the UK, you will have to check ALL of your belongings. Wallets, IDs, and necessary medications are the exceptions, and must be carried in a plastic bag (clear bags are recommended).
  • Laptops, mobile phones and iPods are among the electronic items banned in carry-on luggage on British flights.
  • Liquids, gels, and pastes are no longer permitted in carry-on luggage on board any aircraft within the U.S. and UK (This includes toothpaste, sunblock, and perfume.)
  • Please check our website for updates and the latest information.

So, I follow that link and come across this page, which doesn’t mention laptops, mobile phones, or iPods.

Does anybody know what the current restrictions are for flights to and from the US and UK?

Apache, Typo, and Feedburner

September 08, 2006

A few weeks ago, I started using FeedBurner and posted a blog entry about how I configured Lighttpd to handle that so it didn’t disrupt everyone that subscribes to my RSS feed. This was working great… until the other day.. when I upgraded to Typo trunk. When I did this, I decided to start using mongrel::cluster and pound. Two days later… I’m noticing that my subscriber count has dropped over thousand people in a day… was it something that I said?

A ha! I was handling the redirect with Lighttpd and had replaced it with Pound.

So, I am now delegating this to Apache.

# Redirect typo feeds to FeedBurner
RewriteCond %{HTTP_USER_AGENT} !^FeedBurner.*$
RewriteRule /xml/(atom|rss|rss20)/feed.xml$ http://feeds.feedburner.com/RobbyOnRails [R=temp,L]

…and all was well again.

UPDATE

The rewrite condition should be !^FeedBurner.*$ not !^FeedBurner$.

Injecting Rails into your Legacy World

September 06, 2006

Many of you know that I have an unhealthy obsession with databases… in particular legacy databases. I’m not the only one it seems. :-)

I’m hoping to compile a few stories of how Rails enthusiasts have been able to take advantage of the Ruby on Rails framework within a Legacy environment, whether that be to talk with legacy databases, web services, or a piece of cauliflower. If you have a story (good or bad) of how you used Rails with a legacy system, please email me and let’s talk. :-)

Also, I would like to announce that I have started a new google group that focuses on the topic of using Rails with legacy environments. Check out the new Rails and Legacy group.

If you’re down in California, you can see my talk, “Rails meets the Legacy World” at the Ruby on Rails Seminar, which is being hosted at the AJAXWorld Conference & Expo.

Typo upgraded to trunk

September 05, 2006

I upgraded my blog to Typo trunk this evening. I hadn’t updated since late last year… so it was long overdue. I only had one issue with a migration from a while back.

old revision: 761

current revision: 1258.

I’m impressed that the upgrade worked so nicely… last year the migrations were a bit rough. :-)

UPDATE

I’m also now running this on mongrel with pound! I followed the configuration here.

Agile Interaction Design

August 30, 2006

I would like to start some dialogue with all of you…

In a recent post, Jeremy Voorhis said the following about About Face 2.0 in his post announcing his Agile Book Club.

About Face 2.0 isn’t bad; it’s full of some
great advice. My biggest gripes with it are the follows:

  • It declares that programmers are just unfit for interaction design.

  • It advocates for waterfall development.

  • Cooper has a defensive tone whenever discussing his beloved discipline
    of interaction design.

  • The web chapter is dated.

If you can get over all of those things, it is full of great ideas,
specifically about working with personas, and data entry and retrieval.

I disagree with a few of these conclusions. In particular, that Cooper advocates waterfall development. I’ve been hearing a lot of developers throw the word, “waterfall” around… but why?

Take the following excerpt from this great conversation between Kent Beck, the father of XP, and Alan Cooper.

“During the design phase, the interaction designer works closely with the customers. During the detailed design phase, the interaction designer works closely with the programmers. There’s a crossover point in the beginning of the design phase where the programmers work for the designer. Then, at a certain point the leadership changes so that now the designers work for the implementers. You could call these “phases”—I don’t—but it’s working together.”1

I’m curious as to how anyone would consider this to resemble Waterfall, which might imply that Cooper’s approach to Interaction Design is incompatible with the principles behind the Agile Manifesto.

Dave Churchville posted an article last year titled, Agile Interaction Design?, which discussed how the role of an Interaction Designer (ID) can be compatible with Agile methodologies. “An ID team probably becomes the voice of the customer in Agile methods, and as such should be working closely with the development team as well as the users. In that sense, the ID role may be more of a liaison between customer and developer.”

So, do you think that Interaction Design as described by Alan Cooper… is compatible with the principles of the Agile Manifesto?

UPDATE It looks like this conversation was picked up on the Joel on Software discussion boards.


  1. <http://www.fawcette.com/interviews/beck_cooper/page8.asp>↩︎

Testing Cookies in Ruby on Rails

August 28, 2006

Over the weekend, Brian Ford released a useful plugin for testing your Ruby on Rails applications called, assert_cookie.

Brian likes his cookies…

“I love cookies. There are, of course, tons of varieties and I’m no connoisseur but I love the soft chocolate chip right out of the oven, hot and gooey. But, if you’re like me, you don’t want your Rails code to be gooey.” -Brian Ford

To use assert_cookie, follow these steps.

  1. Install via, script/plugin install http://svn.planetargon.org/rails/plugins/assert_cookie
  2. Fill your tests with some cookies
  3. Test your cookies!

Here are a few examples that Brian posted.

  assert_cookie :pass, 
      :value => lambda { |value| UUID.parse(value).valid? }
  assert_cookie :yellow, :value => ['sunny', 'days']
  assert_cookie :delight, :value => 'yum'
  assert_cookie :secret, :path => lambda { |path| path =~ /secret/ }, 
      :secure => true

For more information on other plugins and tools that PLANET ARGON is releasing under open source licenses, visit www.planetargon.org.

Also, be sure to subscribe to Brian Ford’s feed as he says he’ll be announcing more plugins and tips soon. :-)

Have Fun!

Information Anxiety and Solutions

August 22, 2006

Last week, Allison brought me in a copy of a book that she owns by Richard Saul Wurman. In 1976, Wurman coined the phrase, information architect. (read more)

In his book, Information Anxiety 2, Wurman discusses how we’re overwhelmed by too much information… amongst other related topics.

Allison bookmarked a page for me that discusses the problem with developing solutions without a good understanding of the problem.

“Before any solutions to any undertaking can be developed, a movement must begin to discover its beginning. Understanding the vein of the problem is the course to solving it. The best way to accomplish any endeavor is to determine its essential purpose, its most basic mission. What is the endeavor supposed to accomplish? What is the reason for embarking upon it? This is where the solution lies.”

  • Richard Saul Wurman, Information Anxiety 2

Wurman then goes on to suggest, “There are two parts to solving any problem: What you want to accomplish, and how you want to do it. Even the most creative people attach issues by leaping over what they want to do and going on to how they will do it. There are many how’s but only one what.”

There are many how’s but only one what

“You must always ask the question, “What is?” before you ask the question “How to?””

When Brian and I began rethinking how we were extracting information from our clients, it was important to understand why we felt it was necessary. We’re convinced that the more we can enhance our patterns of dialogue with our clients, the more confidence we’ll have in our approach to building solutions that provide them with that they need, not just what they think they need (want).

Next time a client brings you a list of features for their product, please be sure to ask yourself and your client, “why” the product needs them. What are these hows providing their business and user goals?

FeedBurner and lighttpd redirects

August 22, 2006

I haven’t been using feedburner to track counts of subscribers to my feed. I didn’t want to tell everyone to switch their feed URL… so I found this solution for handling this transition through Lighttpd.

First, make sure you are requiring the mod_redirect module.

server.modules              = ( "mod_rewrite", "mod_fastcgi", "mod_compress", "mod_redirect" )

Then add the following… to your lighty configuration.

$HTTP["useragent"] !~ "FeedBurner" {
  url.redirect = (
    "/xml/rss/feed.xml" => "http://feeds.feedburner.com/RobbyOnRails",  
    "/xml/rss20/feed.xml" => "http://feeds.feedburner.com/RobbyOnRails",
    "/xml/atom/feed.xml" => "http://feeds.feedburner.com/RobbyOnRails"
  )
}

Works like a charm!

Thanks to Damien Tanner for putting me on the right path.