4 ms·

>> You're assuming that someone working from the Hamptons is as productive as working from a desk in the office or his own home. I highly doubt this is true and

>> You're assuming that someone working from the Hamptons is as productive as working from a desk in the office or his own home. I highly doubt this is true and especially so for young junior employees. I've had co-workers in these situations for a long time. In theory there is no difference. But then... - suddenly you can barely hear someone on a conference call because they are on a 4G-tether on a beach, - or because there are tons of bar sounds in the background on a call - or you have a production issue but cant get the person to screen-share because they are on low-bandwidth I even had individuals who would block their entire calendar on WFH days and only take meetings on in-office days. The problem is with those who abuse privileges, not with those who are honest.

ipaddr 3y ago
Blocking off the day makes sense because you want get work done. Meetings can wait until I'm at the office because I'm too distracted to get real work done in my flex-desk. Who cares if employee works at the beach? You need to provide value not appearance of value.
- TuringNYC 3y ago
  >> Blocking off the day makes sense because you want get work done. I'm sure there are cases there it doesnt matter, but I was mentioning cases where teams need to work with each other and are paid to work with each other. I specifically mentioned Production Support. How can production support meetings "wait until they are back at the office?" From my standpoint, it doesnt matter where they are (home or office) but if they have no connectivity and cannot jump into troubleshooting meetings during business hours, i'm not sure how this works for numerous situations. Through my career, i've been on the hot-seat as live applications have gone down. Imagine a DB is down or a pipeline is broken, and my DBA co-worker says "sure, lets take it up on Monday when I'm back". Note, I have no admin rights to the DB. I had a k8s cluster run out of disk space. I had no admin rights to fix this. If the k8s admin decided he could take the meeting a day or days later, it would be a total disaster.

ipaddr 3y ago

Blocking off the day makes sense because you want get work done. Meetings can wait until I'm at the office because I'm too distracted to get real work done in my flex-desk. Who cares if employee works at the beach? You need to provide value not appearance of value.

TuringNYC 3y ago
>> Blocking off the day makes sense because you want get work done. I'm sure there are cases there it doesnt matter, but I was mentioning cases where teams need to work with each other and are paid to work with each other. I specifically mentioned Production Support. How can production support meetings "wait until they are back at the office?" From my standpoint, it doesnt matter where they are (home or office) but if they have no connectivity and cannot jump into troubleshooting meetings during business hours, i'm not sure how this works for numerous situations. Through my career, i've been on the hot-seat as live applications have gone down. Imagine a DB is down or a pipeline is broken, and my DBA co-worker says "sure, lets take it up on Monday when I'm back". Note, I have no admin rights to the DB. I had a k8s cluster run out of disk space. I had no admin rights to fix this. If the k8s admin decided he could take the meeting a day or days later, it would be a total disaster.