I’m a software engineer and a digital nomad. I write code from wherever I happen to be, and I mentor other engineers who want to do the same. This post is about what that mentorship actually looks like.
What I can help with
I’ve kept a real engineering job while moving between time zones and bad WiFi, so I know where this breaks down. Mentoring sessions usually cover one of a few things:
- Staying productive while moving. Time zones, unreliable connectivity, and the discipline of shipping when your day job is in another country. The hard part isn’t the travel; it’s keeping output steady when nothing about your setup is.
- The engineering work itself. Algorithm and system design, working through a problem you’re stuck on, or a code review of something real you’re building.
- Career questions. What to learn next, how to read the job market, whether the role you’re in is the one you should stay in.
I don’t do generic pep talks. Bring a concrete problem and we’ll work on it.
Why take advice from me
I do this for real, not in theory. Over three years and ~60,000 miles we drove the entire Pan-American Highway, from Ushuaia at the bottom of Argentina to Tuktoyaktuk on the Arctic coast of Canada — the whole length of two continents. The whole time I was the maintainer of SecureDNA. So when I say you can hold a serious engineering job from a truck with bad WiFi, I’ve done exactly that. You can follow the travel side at ElTruckito.com.
Booking a session
If any of this is useful to you, book a session with me on ADPList.org. Tell me what you’re working on beforehand so we don’t spend the call figuring out what to talk about.