3 ms·

Standard stuff: 1. “Cross-Nation employment laws and Regulations are hard. “ Yep. You end up not employing people from incompatible places. 2. “It’s hard to d

Standard stuff: 1. “Cross-Nation employment laws and Regulations are hard. “ Yep. You end up not employing people from incompatible places. 2. “It’s hard to do projects that require access to unique equipment.” Yep, these people don’t have remote jobs. Just like a gas attendant or a barber doesn’t. 3. “Communication and Focus is harder.” Yep. I posit that this is you reflecting a desire to mimic the same patterns you enjoyed from the office. That stuff is hard when remote, and for some people it’s just impossible. Those people probably also don’t have remote friendly careers, and that’s ok.

sam0x17 6y ago
The caveat on (2) though is that you _can_ do R&D entirely remotely these days except in industries that require very large equipment that you couldn't set up at someone's house or home office. And in those industries, a lot of the R&D is done in autocad or virtualized environments anyway. Prototyping similarly has been revolutionized by 3D printing.
- LeifCarrotson 6y ago
  I work in industrial automation, with CNCs, robots, HMIs, and PLCs that have huge price tags and footprints. Yes, you'll eventually have to be on site to integrate the equipment, and making anything actually move while not on-site is a big no-no, but between a little simulation, a VPN, and maybe a controller, good development practices make it easy to work remotely. Also, all our machines for several years now have included industrial VPN appliances so we can do remote support and updates - an Ewon Cosy is way cheaper than even an engineer's airline ticket - we just use them a little earlier now. I used to have a wireless router in the shop so I could do development from my office with its desk, monitors, keyboard, and chair. Now that router also runs OpenVPN so I can do the same from home. It's only the non-technical staff that think workers have to be warming seats and shifting steel to be getting work done. A huge amount of building those machines is spreadsheet wrangling and rote business logic connecting inputs to outputs, which is more effective when working remotely than on-location.

sam0x17 6y ago

The caveat on (2) though is that you _can_ do R&D entirely remotely these days except in industries that require very large equipment that you couldn't set up at someone's house or home office. And in those industries, a lot of the R&D is done in autocad or virtualized environments anyway. Prototyping similarly has been revolutionized by 3D printing.

LeifCarrotson 6y ago
I work in industrial automation, with CNCs, robots, HMIs, and PLCs that have huge price tags and footprints. Yes, you'll eventually have to be on site to integrate the equipment, and making anything actually move while not on-site is a big no-no, but between a little simulation, a VPN, and maybe a controller, good development practices make it easy to work remotely. Also, all our machines for several years now have included industrial VPN appliances so we can do remote support and updates - an Ewon Cosy is way cheaper than even an engineer's airline ticket - we just use them a little earlier now. I used to have a wireless router in the shop so I could do development from my office with its desk, monitors, keyboard, and chair. Now that router also runs OpenVPN so I can do the same from home. It's only the non-technical staff that think workers have to be warming seats and shifting steel to be getting work done. A huge amount of building those machines is spreadsheet wrangling and rote business logic connecting inputs to outputs, which is more effective when working remotely than on-location.