Archive for the ‘Amtrak’ Category

Amtrak series: Ruby on Rails on Rails

Thursday, June 7th, 2007

This will be the most technical of my posts in the Amtrak series, but it’s not just for computer geeks so stay with me. Here we go.

Ruby on Rails is a “web application framework”, a way for programmers to make web applications more easily and more quickly (and more enjoyably, as its creators would be quick to point out.) It was created by 37signals, the makers of Basecamp and other fine web apps, and has been one of the fastest growing programming environments of the last couple years. “Ruby” is the programming language and “Rails” is the set of additions that make it “fast” and “easy,” like a high-speed train. (Not a sight-seeing Amtrak.)

img_0088.jpg

You probably see where this is going. As an exercise in literalness, I though it would be interesting to do a little Ruby on Rails programming while on the train, or in other words, Ruby on Rails on Rails. (Mitch Hedberg said “I’d like to see a forklift lift a crate of forks. It’d be so…literal. ‘Hey, you’re using that machine for its exact purpose!’”) See the pictures.

I have not delved into Rails as much as my local colleagues, but with the little I’ve used it, I’ve been impressed. By taking away the tedious parts of programming, it really does make programming more enjoyable. I know several good developers who prefer it.

Ruby on Rails enforces an architecture called “Model-View-Controller” (MVC), which is used heavily in Mac applications and well written web applications. Though not built on Rails, WordPress also uses an MVC architecture. If you have a WordPress blog, you know you can easily change the theme of your blog. This is thanks to the modular MVC architecture with which it was written.

img_0096.jpg

Here’s where this applies to everyone: 37signals hasn’t only extracted Rails from their best programming practices, they’ve also extracted a book from their best business practices. I highly recommend Getting Real by 37signals, availably entirely for free on their website. They’ve given away their “cookbook” — what they’ve learned about marketing, project management, time management, hiring, agility, task prioritization, and more. I finished the book believing that small teams can do great things.

If you want to be notified the next time I write something, sign up for email alerts or subscribe to the RSS feed. Thanks for reading.

Amtrak series: Pictures

Wednesday, June 6th, 2007

More substance to follow tomorrow, but here are some pics from the train ride.

The other side of the rail guard

Other passengers

The curve of the train

The highway below

In the Sierra Nevadas

The Jordan River between Salt Lake City and Provo

My train leaving me behind

Walking home along the railroad tracks

More Photos

Amtrak series: Pick good metrics and stay on track, if it matters

Tuesday, June 5th, 2007

As I mentioned, this weekend I came from Sacramento to Provo by Amtrak train. I flew to Sacramento on Southwest Airlines, buying a one-way ticket so I could decide later whether to depart from SAC or San Francisco. But at the last minute I instead decided to indulge my long time desire to ride a train. (I had long talked of hopping a train with my college roommate, but we never learned if it’s a misdemeanor or a felony and I didn’t think want to risk the latter.)

The ride took 21 hours, which afforded lots of time for reading, listening to music and talks, and taking pictures. I also met several people: a guy moving with everything he owned to start a new life in Denver, an artist-musician couple vacationing (the wife said Steve Case, founder of AOL, asked her to high school prom but she turned him down), and a guy from Wisconsin who’s been in the military for 24 years and thinks we should have gone to Darfur long ago. All very different and interesting stories.

The price for this trip, not including dinner in the dining car, was $74.00 or $3.52/hour. Compare that with my Southwest flight which cost a whopping $37.92/hour.

But when did the price per hour of a trip ever matter?

If you want to accomplish something, you must measure it:

If you don’t measure something, you can’t change it. The process of leadership is one of painting a vision, then saying how you’re going to get there, and then measuring whether you’re actually getting there. Otherwise, you risk only talking about great things but not accomplishing them. (Source: Mitt Romney)

I like the idea of using metrics to incent the right behavior. For example, “cars with realtime MPG usage displays tend to make people more efficient drivers.” (source, also) If you keep track of how often you read important books or go to the gym, or how meaningful your time is with your family (even in a subjective sense), those things are sure to improve over time. Pick your own metrics and stick to them.

More on metrics: High resolution mistakes by Seth Godin and Domino Rally business models by Paul Allen

So what could possible be meaningful about a trip with a low price per hour? That metric could only incentivize inefficient, slow-paced trips with no regard for urgency or schedule. Or in other words, I was just in this one for the ride.

Series of posts on Amtrak

Monday, June 4th, 2007

This weekend I flew to Sacramento for my cousin’s wedding. I decided to return by train, so I bought an Amtrak ticket and arrived this morning after a 21 hour ride. This week I’m going to write every day about my trip.

The Amtrak Series