No Office, No Problem: The Remote Work Setup That Never Quits

It’s 2:47 PM on a Tuesday. Three houses down, a girl is turning fifteen, and her family has rented a sound system that could probably scramble flight radar. The neighbour’s parrot is screaming back at the reggaeton. Two roosters across the yard, who I am convinced after five years here have never once seen a sunrise, are losing a turf war. A vendor truck just rolled past announcing tomatoes through a loudspeaker bolted to its roof.

I have been on a Google Meet, camera and microphone live, for the past six hours.

Nobody on the call has heard a thing.

This is the setup. This guide is everything I’ve learned building it.

The short version of where I am

I work remotely from Central America for a North American company. My boss thinks I’m in Canada. He’s a micromanaging type who decided the cure for distributed teams was an all-day Google Meet, cameras on, mics open, “just like the office.” It’s an absurd policy. I’ve worked under it for over six months. Nobody has noticed where I actually am.

It wasn’t always like this. When I went remote years ago, I had a laptop, a router, a coffee mug, and the optimism of someone who hadn’t yet experienced their first apagón (power outage) mid-call. Or their first Quinceañera (a wedding-scale fifteenth-birthday party with a DJ, a full bar, and all-night block volume). Or the day the maid decided to vacuum during a client demo. The fruit seller. The first storm on a tin roof. The four-hour outage on payroll day.

Everything in this series exists because something in my life broke (sometimes literally, sometimes just professionally) and I had to engineer my way out before the next time it happened. The end result is a stack that hasn’t dropped a call in months. Plenty has gone wrong. The point is that nothing that’s gone wrong has reached the other end of the line.

This is for anyone working remotely from somewhere that isn’t a sterile suburb of Toronto. The hot places. The loud places. The places where electricity is more of a suggestion than a guarantee, where a Tuesday afternoon parade is a reasonable scheduling concern, and where your ISP technician’s ahorita (literally “right now,” practically “sometime between this afternoon and never”) can leave you waiting for a week with no internet. If that’s your life, or the life you’re about to move into, read on.

The one big idea: nothing should be a single point of failure

If your work depends on something (power, internet, audio, a laptop, a quiet room), you need a backup. If the backup is critical, you need a backup for the backup. Each layer doesn’t have to be as good as the one above it. It just has to be good enough to keep you running until the layer above recovers. Or until you can hand off to the next thing.

That sounds like overkill until the day it isn’t. The day a girl turns fifteen, the grid drops, your ISP guy ghosts you with an ahorita, and your boss pulls you into an unscheduled call with the CEO. On that day every redundant layer earns a year’s worth of its cost in the first ten minutes.

The rest of this series breaks the stack into six pieces. Read them in order or jump to whatever’s currently broken.

Layer 01 / The Hardware

Three laptops, never one

I have killed two laptops working remotely from Central America. One was a thin-and-light with a 15-watt ULV chip that overheated within four months — the screen died mid-call-centre shift, vertical pink lines and a customer still talking. The next was a gaming laptop I bought for the spec sheet: great on paper, jet-engine fan whine on every call, cracking plastic chassis by month eight. It got donated to a friend who actually plays games.

Two dead machines taught me to stop guessing. The setup now runs three machines doing three different jobs. The workstation handles everything heavy. The second is a dedicated video call device, positioned where the fans don’t blow noise into its microphone, running nothing but the all-day Meet. I control both from one keyboard and mouse via a software KVM. The third is a backup and personal machine — sitting ready. If anything goes sideways with either of the first two, I’m not announcing the fact.

Article 02 / Read the full guide The Best Workstation Laptops for Remote Work Anywhere Why one laptop is a single point of failure, what to look for in each role, and the gotchas of running three machines side by side with a software KVM. → Layer 02 / The Audio

Noise is the thing that gets you caught

Before I sorted out the noise problem, every workday felt like trying to play violin in a kitchen during a fire. Two fans pointed at me. A maid running a vacuum. Reggaeton from somewhere I could never quite triangulate. Vendor trucks. Roosters. A washing machine spinning into the off-balance death rattle on the other side of a wall.

And me, on camera, on mic, with a colleague in Toronto saying wait, what was that?

You can solve almost all of it with three layers stacked on top of each other. There’s hardware in the call laptop’s microphone that handles the first pass. There’s software running on top of that for the second pass. Then there’s a proper headset for client calls when the audio has to actually be good, not just clean.

Stack all three and you can take a call from a house with a tin roof during a wet-season thunderstorm with the fans on full and a parade going past.

Article 03 / Read the full guide Noise Cancellation for Remote Workers Each of the three layers, the gear categories worth paying for, and the underrated acoustic work that closing a single door does. → Layer 03 / The Power

The grid will leave you. Be ready.

The first real apagón I sat through as a remote worker happened ten minutes into a call with the head of finance at my company. The lights went out. The router went out. The laptop went onto its internal battery and started screaming about being unplugged. The Wi-Fi died. I sat in the suddenly-quiet, suddenly-dark room and watched my Meet window helplessly try to reconnect.

Then I lied through my teeth in a Slack message and pretended my building had a fire drill.

Now, when the grid drops, nothing happens. The laptops stay on through their UPS units. The router and modem stay on through a separate, smaller DC UPS that bypasses the inefficiency of running networking gear off AC power. Two big USB-C battery banks sit on the desk for laptop top-ups. A smaller bank handles the phone. With CPU power-limiting software pulling the laptops down to a sip when they’re on battery, I can run an entire workday on no mains power. Two days if I scale down to just the lightest machine.

Power is the most-bookmarked article in this series for a reason.

Article 04 / Read the full guide Power Redundancy for Remote Workers UPS sizing, the DC UPS for your router that almost no one talks about, the battery banks worth owning, and how to layer all of it together. → Layer 04 / The Network

Your home base should travel with you (without leaving home)

When you’re working remotely from somewhere you’re not officially supposed to be, three things matter. Keeping the connection up. Making sure your traffic looks like it’s coming from where your work systems expect it to come from. And having a familiar machine you can drop into when something local breaks, or when you need to be unambiguously “at the office.”

A commercial VPN doesn’t really solve any of these. The endpoints are datacentre IPs that serious work systems flag and block. It doesn’t connect your own devices to each other. And it hands all your traffic to a company you’ve never met.

The setup I run instead has two parts. First, a private mesh network with small computers running as residential exit nodes at friends’ houses back in Canada, so my traffic appears at a residential IP in my home country whenever it needs to.

Work systems see Canada; I see ocean.

Second, a small always-on PC at home that I can remote into from anywhere in the world. It runs auto-login, auto-reboot on power failure, a virtual display dongle so the graphics card behaves with no monitor plugged in, and a vPro-capable motherboard so I can recover the BIOS remotely if it ever gets truly stuck. RDP is the daily driver. A few other remote desktop tools sit alongside it as backups for when one of them inevitably acts up.

Article 05 / Read the full guide Your Remote Home Base: Tailscale + Always-On Home PC + Layered Remote Desktop The mesh network, the residential exit nodes, picking and configuring the home PC, layering the remote desktop tools, and the travel-router trick for locked-down corporate laptops. → Layer 05 / The Endgame

Making the grid optional

Everything above is a reactive system. The grid drops, the UPS picks up, the batteries stretch, you make it through. It works. It’s saved me dozens of times. But it’s all still responding to the failure of infrastructure you don’t control.

There’s a higher tier. You generate your own power. Your house runs on the sun. The grid becomes an occasional supplement, or it becomes irrelevant. The UPS gear stays in the stack as final-layer insurance, but day-to-day you stop caring about apagones (power outages) entirely.

The right shape for most people is a hybrid solar system: panels on the roof, a battery bank inside, a hybrid inverter tying it all together with the grid. When the grid drops, the inverter switches to running the house from solar and battery in milliseconds. You don’t notice. The call doesn’t drop.

It’s an investment, not a casual purchase. But if you’ve committed to a location and the grid where you live is anything less than rock-solid, the math changes fast.

Article 06 / Read the full guide The Off-Grid Solar Work Setup Daily load calculation, panel and battery sizing for your peak sun hours, what to look for in a hybrid inverter, and what’s actually available in Latin America right now. → Layer 06 / The Lessons

The expensive lessons

A lot of this stack exists in its current form because earlier versions failed. The first headset I bought sounded great in a quiet apartment back in Canada and picked up every fan I owned the moment I tested it here. The first UPS I bought lasted ninety seconds under real load. The first ISP I trusted had a reliability number on their website that turned out to be aspirational bullshit.

Most of the gear in articles 2 through 6 is on its second or third iteration. I’ve spent more money learning what doesn’t work than I have on what does.

If you’re buying any of this for the first time, this article will save you the most money out of anything in the series.

Article 07 / Read the full guide Everything I Got Wrong The expensive, dumb mistakes I made building this setup. Read this first if you’re about to spend money on any of the above. →

One last thing

The setup in this series isn’t aspirational. It’s just what’s running, right now, while a teenager three blocks away is being celebrated at volumes that violate three or four laws of physics, while a fan is pointed at me to keep me from melting, while my boss is asking me to share my screen.

It took years and a fair bit of money. Not all at once, and not all expensive. Most of the gear pays for itself the first time it stops you losing a day. Build it up the way I did. One piece at a time, usually right after something new just broke.

By the time the next Quinceañera starts, you’ll be ready.

The whole stack at a glance

Up Next — Article 02 The Best Workstation Laptops for Remote Work Anywhere →