I almost titled this post “Wasting Company Time & Burning Yourself Out” considering some of the interactions and involvement I’ve seen in the DevRel Community of late. But I’ll get to that drama and angry frustrations later in the post, but immediately let’s get down to brass tacks.
As I dive into the nuances of traveling as a Developer Advocate, it’s crucial to clarify that this post isn’t just about logistics or coping mechanisms, but about the larger strategic picture beyond just the tactical underpinnings of day to day travel, airports, train stations, and the like. Instead, I aim to delve into what underpins the demand for travel as a developer advocate. Travel is far more than just getting from point A to point B to partake in an action. It’s about positioning myself—and by extension, the organizations and efforts I represent—to make meaningful connections, drive impact in decisions, and stay ahead in a rapidly evolving industry.
Strategic Travel: Guiding the Future of Major Projects
When it comes to strategic trips, the stakes are high. These aren’t just any industry conferences or casual meetups; they’re focused events where the future of a project might hang in the balance. Take, for example, a situation where a software fork of a major open-source project is on the horizon. The decision to fork isn’t taken lightly—it’s a move that could redefine the project’s trajectory, influence developer adoption, and ultimately shape the software landscape for years to come. Being on the ground and having built connections with the people involved face to face is irreplaceable. Having just had few meetings or video conf calls doesn’t cut it, one can’t replace the built trust of time spent face to face builds. This is where traveling to where people are, as an advocate, become priceless.
In these scenarios, my travel is centered around influencing and guiding these pivotal moments. I’m there to represent the interests of my company, to ensure that our vision and goals align with where the project is heading. This might involve meeting with the core contributors, understanding their motivations, and providing insights that can help steer the project in a direction that benefits both the community and the enterprise. It’s about being at the table when decisions are made, rather than reacting to them after the fact.
Similarly, when a new, large organization steps in to take over governance of a project, the dynamics can shift dramatically. My role here is to establish relationships early, understand the new leadership’s vision, and offer strategic input that aligns our goals with theirs. This isn’t about forcing our agenda—it’s about finding common ground where both parties can thrive.
Tactical Travel: Building Connections in the Industry
On the tactical side, the focus is more granular but equally important. Every trip to a conference, meetup, or industry event is an opportunity to meet, learn from, and exchange ideas with peers across startups, SMBs, and large enterprises. These interactions are where I gather insights on how different organizations are tackling similar challenges, what tools they’re using, and what their desired outcomes are.
For instance, attending a conference might put me in touch with a key decision-maker at a startup that’s just beginning to scale. They’re facing challenges with their CI/CD pipeline, and they’re considering a move to a new platform that I’ve been advocating for. Through our discussions, I can provide them with the insights they need to make that decision confidently, while also gaining a deeper understanding of the pain points that are driving their choices.
Similarly, meetups offer a more informal setting to connect with the implementers—the engineers and developers who are in the trenches, building out the solutions that will power tomorrow’s technologies. These conversations are invaluable. They allow me to see firsthand how our tools and platforms are being used in real-world scenarios, and they provide an opportunity to gather feedback that can be fed back into our product development cycles.
In every tactical interaction, my goal is to build relationships that extend beyond the immediate conversation. I’m looking to understand the missions of the people I meet—what are they trying to achieve, what challenges are they facing, and how can I help them get there? These connections are the lifeblood of developer advocacy, and they’re what make the travel worth it.
Managing Travel as a Developer Advocate: Balancing the Chaos
With the strategic and tactical intent in mind, the actual process of managing travel becomes a critical component of the job. Travel as a Developer Advocate isn’t just about attending events; it’s about maximizing the impact of every trip while maintaining personal and professional balance.
The Art of Pre-Travel Prep
Preparation is where it all starts. Before I even think about boarding that plane, train, boat, or whatever my mode will be, I make sure my travel plans are bulletproof. This means having a clear itinerary, knowing the lay of the land in the cities I’m visiting, and ensuring I’ve got all the necessary tools and backups for work.
Itinerary: A well-planned itinerary is crucial. It’s not just about knowing which sessions I’m speaking at or what meetings I have lined up. I go deeper—knowing where the local coffee shops are (because who can function without a good coffee?), having a couple of backup restaurants that cater to my dietary preferences, and being aware of the quickest routes to my hotel or the event venue. Google Maps is my best friend here, and I often create custom maps to keep all this info in one place.
Tools & Backups: As a Developer Advocate, my gear is my lifeline. This includes the obvious—laptop, charger, phone—but also the not-so-obvious. I always carry a portable battery pack, a universal adapter, and a mini Ethernet cable (you never know when Wi-Fi might betray you). Cloud backups are a must; I make sure all my important files and presentations are synced to a secure cloud service before I even leave the house. It’s also not uncommon for me to bring or ship ahead of time key assets for redundancy; a laptop, thumb drive with collateral on it, or other items. Because even a cloud backup isn’t insured against a conference just having bad wifi or wifi that won’t enable you to download something last minute!
Navigating the Travel Hustle
Once on the trip, the hustle begins. Airport lounges, train stations, hotel rooms, coworking spaces, and event centers become my makeshift offices. Here’s how I keep it all running smoothly.
Time Zones & Sleep: Jet lag is real, maybe I’ll speak specifically about how I deal with it one day. But for now let’s focus on the fact it can derail your productivity fast. I’d suggest trying to adapt to the new time zone as quickly as possible by adjusting your watch as you board the plane, start living in that time zone the moment you’re in route.
International: If you’re traveling internationally it’s good to check what you’ll have or not have access to. For example if you’re going to China, forget the Internet. If you’re going to Russia, we need to have a talk, write me on the contact form about the worst ideas you could have. If you’re traveling to most of Asia (India, Japan, etc) you can have vastly different quality of service and various other ramifications to deal with. In Europe you’ll likely have great service but there will be nuances to deal with. For example, the age old Netflix issue, you’ll have a whole new slew set of shows depending on what is licensed where. Be prepared for this, look up the details of where you’re going, and work to mitigate the issues.
Staying Connected: Reliable internet is a necessity. I make sure I have an international data plan or a portable Wi-Fi device that works in the countries I’m visiting. The last thing you want is to be stuck in a situation where you can’t access the internet, especially if you’re about to go live on a webcast or need to push that critical code update.
Health on the Go: Travel WILL take a toll on your body that over time isn’t particularly positive. You absolutely have to actively work – A LOT – to mitigate the harmful effects of wearing yourself out traveling. I’ve made it a point to maintain a healthy routine while traveling, staying active, and also being sure to hydrate appropriately (especially with air travel). I carry a water bottle to stay hydrated (yeah yeah yeah very “American”), pack some healthy snacks to avoid the temptation of junk food, and I often get a work out by bringing my Brompton, a full size bike, or even rent one for use on trips. Basically, I stay as close to active while traveling that is similar to how I live. If you don’t, all the negatives will come after you: extra tiredness, weight gain, hydration issues, extra stress, you name it! You gotta do things that will work for you, so obviously it’s a learned experience once you’re out there, my advice is to keep this top of mind. Not a little toward the top, but literally the TOP of mind, first thing you start dealing with anywhere you go.
What Makes a Good Trip?
A successful trip is one where both strategic and tactical goals are met without disrupting the core mission of advocacy. The ideal trip balances advancing the broader objectives—such as influencing a major project’s direction or building new industry relationships—with the day-to-day work of staying deeply connected to the technology, product, or solution at the heart of the advocacy role.
A good trip ensures that even while attending conferences, meeting with key decision-makers, and exploring the latest trends, there’s still time to maintain the rhythm of work that keeps me on top of the technology I’m advocating for. It’s about keeping up with the latest developments, prototypes, and product updates, ensuring that my knowledge remains current and my advocacy effective.
However, too much travel can be counterproductive. It’s easy to lose touch with the core underpinnings of the technology if you’re constantly on the road. The balance is delicate; typically, 1-3 trips per quarter is ideal. This cadence allows enough time for learning and growing with the technology while still making meaningful connections through strategic and tactical travel. Anything beyond that increases the risk of disconnecting from the very core of what makes advocacy successful: an intimate, ongoing engagement with the technology and community you’re representing.
The Wrap Up
Travel as a Developer Advocate is a multifaceted challenge that demands a balance of strategic foresight and tactical execution. Whether guiding the future of a major project or building connections at industry events, each trip is an opportunity to make a meaningful impact. By preparing thoroughly, staying adaptable on the road, and reflecting on the journey, I can ensure that every trip contributes to my goals as a Developer Advocate.
But beyond the immediate goals of each trip, it’s crucial to maintain a consistent connection to the technology, product, or service being advocated for. Too much travel can create a disconnect from the very mission of advocacy. The key is to strike a balance—traveling enough to build strategic relationships and gather insights, but not so much that it disrupts the deeper work of staying connected to the technology and community.
In the coming posts, from my own experiences and from my interest in developer advocacy, I’ll explore strategies for maintaining this balance, ensuring that travel enhances rather than hinders the mission. I’ll delve into how to manage efforts effectively when balancing trips to conferences, meetings with customers, and other events with the day-to-day work that keeps a Developer Advocate grounded and effective. For good measure, I’ll throw in some bike tips here and there! Stay tuned!
