// I need to

ModernizeUpgrade without breaking it RescueFix what someone else started Build NewTurn an idea into a product Reach More PeopleGet found, get used, include everyone

// Company

Case StudiesExpertiseAbout + CareersResourcesContact Book a call →
≡articleBuild New

Working from Amtrak

Remote work by rail: a month-long Amtrak trip across the United States, coding from observatory cars with a light laptop and cellular tethering.

Art+Logic Apr 16, 20131 min read

From the Art+Logic archive · written in 2013. The tools may have moved on; the thinking still holds.

Telecommuting often means working from home, a coffee shop, or a coworking space.  But freedom from an office can open up a broad world of possibilities.  For me, that translated into an Amtrak rail pass and a month-long perambulation of the United States, where my workspace has been observatory cars and friends’ apartments paired with a lightweight laptop and cellular tethering.

Image of train
The Vermonter arriving into White River Junction, VT

My route: Vermont -> New York City -> Philadelphia -> Washington, DC -> New Orleans -> San Antonio -> Austin -> Los Angeles -> San Francisco -> Portland -> Seattle -> Chicago -> St. Louis

When I pull myself away from the scenery and the new friendships found on the train, work itself has been generally smooth.  There’s joy and time for writing code in the long rides, with rolling vistas, power outlets at every seat, and the gentle rumble and rocking of the rails.

The biggest setback has been intermittent connectivity.  Amtrak’s WiFi is only available on a few trains and is often overcrowded, so a Verizon MiFi device or smart phone tethering is a necessity.  Even with those options, though, cell service can be hard to find through most of Montana, and switching cell towers at 70 MPH can make Skype conversations stutter and fail.  I’ve had to plan my calls accordingly, and prep sufficient offline work before the train ranges too far from cities.

Amtrak is also known for exasperating bureaucracy (that becomes unimportant once you’re actually on a train and taken care of by the kind and quirky conductors), and for a penchant for delays (due to mud slides, freight traffic, and inebriated passengers).

With those drawbacks in mind, and a reading of the excellent commentary “Traveling the USA via Amtrak Rail Pass” by a pair of self-styled “technomads”, I’d recommend working from Amtrak to anyone with the travel itch and liberty to roam.

keep going

More to explore in Build New.

All Build New resources →
let's talk

Got a problem like this one?

Tell us what's stuck. A real person replies within one business day.

Talk to our team →

Talk to people who know software, not a sales script.

Your first call is with Aja, our VP of Sales. He'll help make sure you're solving the right problem. Here's what you'll cover together:

  1. What you're trying to accomplish

    The business goal first, then the technology.

  2. Possible approaches

    And the tradeoffs of each, in plain language.

  3. Risks you may not have considered

    Technical and business, before they cost you.

  4. Whether AI changes the math

    What's practical, and what's just hype for your project.

  5. Sensible next steps

    Even if the right next step is not us.

book-a-call.ics

Loading the scheduler…

Open the booking page →

Some problems are easier to explain in writing. Send us a few lines about what you're working on, and we'll reply within one business day. Helpful to include:

  1. What the software does, or should do
  2. What's stuck, or what's worrying you
  3. Any deadline or budget you have in mind
note.md

Loading the form…