2 ms·
No surprises there, but good solid advice that a lot of people need to hear. Well done. The one thing I'd add is that working remotely means working away from
by notacoward 13y ago
No surprises there, but good solid advice that a lot of people need to hear. Well done.
The one thing I'd add is that working remotely means working away from machines as well as people - test machines, internal websites, etc. Even companies that are generally supportive of remote workers (like mine) often scatter essential information and resources across an annoying variety of machines that are not accessible from outside. Then they give you a VPN that's utter crap (usually because it's overloaded) or ssh to a bastion host so you have to tunnel/forward anywhere else. It's really worth the effort to make sure you use every trick in the book to get networking on your home machines and/or laptops set up in a way that actually allows you to get work done. I'm pretty darn good at that kind of stuff, but even so it took me several experiments over a period of weeks to get something I was happy with - and BTW it bears no resemblance at all to what the IT group thought would suffice. Similarly, it pays to make sure that using test machines is as friction-free as possible, and that common tasks are automated as much as possible so that you don't have to keep watching/tweaking things from afar. All good sense even if you're not remote, but even more important when you are.