5 ms·

Going to have to +1 this. I worked remotely/from home for 6 years, and was extremely productive, and also much less stressed. If I needed to take an hour or two

by badwolf 10y ago

Going to have to +1 this. I worked remotely/from home for 6 years, and was extremely productive, and also much less stressed. If I needed to take an hour or two and go to my apartment's pool, then I'd do it... Now I'm back in an office doing 9-5, and everything is a chore. My stress levels are significantly higher than previously, etc... With tools like group video calling, conference calls, email, Slack/chat, etc... It's incredibly easy to stay "close" with your team while being remote.

softawre 10y ago
Right, you are speaking from the employee side though. You seemed to have gloss over the "difficulty getting in touch with someone" and "times when you must be available" part. Depending when you were out at the pool, I can imagine you got a few instant messages from your boss that you didn't reply to.
- walterstucco 10y ago
  that could happen in the office as well
kefka 10y ago
The tools to work remotely can be nice as you put it... But if you can work remotely from home/desk, so can people who are willing to work for 10% of your salary. In person means "Im on the radar, im there to consider, and there to help". Someone over a chat client doesnt have the same presence. Now, this might/probably change with the advent of AR and VR workspaces.
- Touche 10y ago
  > But if you can work remotely from home/desk, so can people who are willing to work for 10% of your salary. That's just capitalism. Choose a profession where you're not so easily replaced by someone who will take 10% of your salary.
- obstacle1 10y ago
  >if you can work remotely from home/desk, so can people who are willing to work for 10% of your salary If you're so unskilled as to be that replaceable, there's no reason to feel comfortable in a non-remote job, either.
- ChoHag 10y ago
  If an employer chooses someone at 10% of your salary, your employer is chooosing someone too stupid to demand 90% of your salary. Do you really want to work for the idiot who's OK with that?
OpenDrapery 10y ago
Productive according to what measurement? The problem is that the tech industry is still failing to measure productivity, even when people are onsite. So the lazy fall back is "butts in seats". If I can see you sitting in you're chair, I think you're productive. If I can't, then you are not. So, while you say you were productive while working remotely, there was some manager who thought you were doing nothing at all.
- deleted 10y ago
  [deleted]
- bpyne 10y ago
  What's an objective measurement for jobs as diverse as software engineer, system administrator, computer technician, and first-tier support? The Tech Industry is made up of these roles and many more. Just take a software engineer for example. LOC is fallible in too many ways to take seriously. Number of function points coded? Number of bugs fixed? They are all very fallible. How about mentoring? How about reviewing code? How about documentation? How about professional development? Depending on the situation, reading a technical article can weigh higher than a support issue. How do you develop the weighting for the different factors? Can it be applied across organizations? To confound it further, people tend to take on work that doesn't fit their title. The smaller the organization, the larger the diversity of responsibilities. Then there are soft factors like knowing which issues to address immediately in order to keep them from percolating up to your manager, working well within a team, communicating effectively, etc. My opinion is that we are unlikely to see objective, effective measurements of productivity for the Tech Industry anytime within my employment life. It's not a failure. The number of factors involved, not to mention the ability to gather the measurements, is staggeringly complex. After all, we're not factory line workers producing pre-defined widgets.

by badwolf 10y ago

softawre 10y ago

Right, you are speaking from the employee side though. You seemed to have gloss over the "difficulty getting in touch with someone" and "times when you must be available" part. Depending when you were out at the pool, I can imagine you got a few instant messages from your boss that you didn't reply to.

walterstucco 10y ago
that could happen in the office as well

kefka 10y ago

The tools to work remotely can be nice as you put it... But if you can work remotely from home/desk, so can people who are willing to work for 10% of your salary. In person means "Im on the radar, im there to consider, and there to help". Someone over a chat client doesnt have the same presence. Now, this might/probably change with the advent of AR and VR workspaces.

Touche 10y ago
> But if you can work remotely from home/desk, so can people who are willing to work for 10% of your salary. That's just capitalism. Choose a profession where you're not so easily replaced by someone who will take 10% of your salary.
obstacle1 10y ago
>if you can work remotely from home/desk, so can people who are willing to work for 10% of your salary If you're so unskilled as to be that replaceable, there's no reason to feel comfortable in a non-remote job, either.
ChoHag 10y ago
If an employer chooses someone at 10% of your salary, your employer is chooosing someone too stupid to demand 90% of your salary. Do you really want to work for the idiot who's OK with that?

OpenDrapery 10y ago

Productive according to what measurement? The problem is that the tech industry is still failing to measure productivity, even when people are onsite. So the lazy fall back is "butts in seats". If I can see you sitting in you're chair, I think you're productive. If I can't, then you are not. So, while you say you were productive while working remotely, there was some manager who thought you were doing nothing at all.

deleted 10y ago
[deleted]
bpyne 10y ago
What's an objective measurement for jobs as diverse as software engineer, system administrator, computer technician, and first-tier support? The Tech Industry is made up of these roles and many more. Just take a software engineer for example. LOC is fallible in too many ways to take seriously. Number of function points coded? Number of bugs fixed? They are all very fallible. How about mentoring? How about reviewing code? How about documentation? How about professional development? Depending on the situation, reading a technical article can weigh higher than a support issue. How do you develop the weighting for the different factors? Can it be applied across organizations? To confound it further, people tend to take on work that doesn't fit their title. The smaller the organization, the larger the diversity of responsibilities. Then there are soft factors like knowing which issues to address immediately in order to keep them from percolating up to your manager, working well within a team, communicating effectively, etc. My opinion is that we are unlikely to see objective, effective measurements of productivity for the Tech Industry anytime within my employment life. It's not a failure. The number of factors involved, not to mention the ability to gather the measurements, is staggeringly complex. After all, we're not factory line workers producing pre-defined widgets.