3 ms·
It's one thing to "develop" in vim over a slow ssh session or VNC. The latency makes that very annoying. But we're at the point where we can still have a lot o
by armchairhacker 4y ago
It's one thing to "develop" in vim over a slow ssh session or VNC. The latency makes that very annoying.
But we're at the point where we can still have a lot of analysis on the machine, and offload the slow analysis and building onto a more powerful computer, so that remote development is faster even with latency. And also getting to the point where internet connectivity is really fast so latency is low.
Like with most systems, the important part of remote development is that it's done well. And it seems like most employees are comfortable with Uber's setup.
Although, I do have to say that most companies really shouldn't use remote development, only if they have some excuse like they're Uber sized so that the benefits outweigh the costs. I've done remote work at uni, and they're servers and integrations aren't nearly as good so it's a chore; it's faster to use Mutagen and just develop locally then build/deploy remotely.