3 ms·
IMO, it wasnt really until 2015 that we had the bandwidth available everywhere to do widespread WFH.
by Aloha 3y ago
IMO, it wasnt really until 2015 that we had the bandwidth available everywhere to do widespread WFH.
- marcosdumay 3y agoYou mean widespread remote meetings? Because there's more to work than meetings. Developers have been very productive in remote-only teams since the 90's.
- Aloha 3y agoRemote meetings are just one problem, I cant imagine trying to run SMB (or even the somewhat lighter NFS) calls over an 144 kbit ISDL or ISDN connection, even on an ADSL connection with a 384 or 768 upstream would be painful. Maybe remote over connections that slow is fine if you're using version control - checking out the changes to the source tree, making changes, and checking them back in - its not okay if you're trying to open/change/save multi-meg excel files, things where you cant make incremental writes to. tbh, the most common way I saw people working remote in the 90's and early 00's was Citrix or similar other remote work tools. The broad thing is, the size of say.. software or scripting when I'm doing that, is a fraction of the size of my project docs, and are often stored to the server asynchronously - when I have to make drawings, its a different world.