Your Claude response comes back in 800 milliseconds. You're on a roll. Three features shipped before lunch. And somewhere, silently, your debugging intuition is going to sleep.
I've been tracking a pattern across developer forums — not just V2EX, but in the back-channels of engineering team chats: developers who live in network-restricted regions are increasingly "renting" computational presence elsewhere. A computer in a data center, a VM in Singapore, a colleague's spare workstation. They connect, they code, they use AI tools that would otherwise be unreachable. Problem solved.
Except it's not solved. It's deferred. And the cost is accumulating in a place most devs never check: the gap between what they can describe doing and what they can actually do.
The Compute Rental Economy
The V2EX discussion that triggered this article described a developer's setup: living abroad, rented room with a desktop computer inside China, wants to remotely access that machine to use Claude's web interface and write code. The comments branched into VPN recommendations, remote desktop protocols, browser-based solutions, and one or two voices asking the question nobody else wanted to answer — why?
