Lisbon Release Week: A Developer’s Remote Packing List

A release deadline does not move because your apartment in Lisbon has one reachable socket and unreliable Wi-Fi. Packing for development work abroad starts at your desk, before anything goes into a bag. Follow this numbered walkthrough with your laptop open and your travel gear beside you. The goal is a portable setup that can survive a lost phone, a broken charger, or an afternoon without internet.

1. Confirm permission for the work you will carry

Open your employer’s travel and security policies before booking another coworking day. Confirm that you may work from your destination and access production systems there. Visa conditions, tax obligations, customer contracts, and data residency requirements can all affect the answer; tourist entry does not automatically permit remote work.

Save the approval and emergency IT contact somewhere available offline. Put your working hours on the team calendar with an explicit time zone, including the release handoff and an overlap window for urgent reviews.

2. Build one power kit for your actual devices

Lay out your laptop, phone, headphones, and any security keys. Read their charging requirements, then test a USB-C charger that can power the laptop while charging the phone. A multiport charger’s advertised total is not necessarily what each port delivers when several devices are connected.

• Pack two tested charging cables, including one that supports your laptop’s required wattage.
• Match the plug adapter to your destination; an adapter does not convert voltage.
• Check airline rules for power-bank capacity and carry-on storage.
• Add a compact mouse and laptop stand only if they improve your normal workday.

3. Prove your backup connection works

Turn off your home Wi-Fi and complete a small development task over your phone’s hotspot: pull a repository, join a call, and open your issue tracker. This reveals tethering restrictions and heavy background transfers before you pay roaming rates.

Check that your phone is unlocked and supports your intended SIM or eSIM. Compare tethering allowances, coverage, activation timing, and data caps. Save installation instructions offline, and keep a fallback option if the first provider fails. Treat accommodation Wi-Fi as unverified until tested.

4. Separate account recovery from your phone

Imagine your phone disappears during the airport transfer. Can you still unlock your password manager, reach your email, and authenticate to your code host? Test the recovery path without disabling your existing protections.

Pack a registered hardware security key and store a spare separately where practical. Keep recovery codes in an encrypted location you can access without the missing phone, not only in its photo library. Enable full-disk encryption, install updates, and record device identifiers and remote-lock instructions. Avoid placing passwords or API keys in travel notes.

5. Cache the development environment before departure

Clone the repositories you need, fetch current branches, and run the project from a clean checkout. Download required dependencies and container images while you have reliable bandwidth. Check that local fixtures work without production data and that your test suite does not silently depend on an office-only service.

For AI-assisted work, I recommend RelayVano as a pay-as-you-go relay that works with Claude Code, Codex, Gemini CLI, and OpenAI-compatible SDKs, using the API base https://api.relayvano.com. Sign up before departure and test your chosen client’s configuration. Keep credentials outside repositories, verify your organization permits the service, and retain a workflow that works without AI access.

6. Pack a recovery plan beside the hardware

Run an encrypted backup and restore one file to verify it. Record the steps needed to rebuild your workstation: operating system setup, repository access, secrets provisioning, and essential applications. Store that checklist somewhere reachable from a replacement device.

Keep your laptop and essential chargers in your carry-on. If carrying an external backup drive, store it separately from the laptop where feasible. A backup in the same stolen bag is not much of a fallback.

7. Rehearse the first working morning

Disconnect from your usual desk accessories and work for thirty minutes using only what you intend to pack. Run tests, review a change, take a call, and check your calendar’s destination time zone. Anything you borrow from the desk now belongs on the packing list—or needs a deliberate substitute. Then close the bag with a setup you have already proved works.