|
|
|
|
|
by lbriner
1615 days ago
|
|
There are lots of reasons why you might suffer a performance hit when working remotely. Sure, most are probably solveable with enough cash but there are plenty of things that are not: * One of your prized developers lives by themself and suffers bad anxiety from being alone all the time instead of in the office * Your 10 year old production systems are designed from the ground-up to be secure from inside a single network. Sure you could add VPNs but then you get a load of other issues * There are people who will only focus when in the office, too many distractions at home and they are less productive. There is no objective way to measure productivity and also what drop would be acceptable so how do you fairly appraise people when you can't see how they interact? * Juniors trying to learn on the job is 100x easier in-person. * All manner of issues with onboarding, hardware, network problems, unannounced disappearances from people that you need to speak to (as opposed to them being in the office and they tell you they need to go to the doctors). Not saying that I don't want to fix these since we need to use remote working to survive probably but you can't pretend these are just things that can be fixed. |
|