3 ms·

I am glad that is your experience.There is no single answer for all people. I think you as an employee are making a wise choice. If you can get paid a full sala

I am glad that is your experience.There is no single answer for all people. I think you as an employee are making a wise choice. If you can get paid a full salary for 20 hours of work, it is in your best interest to keep that alive! As a business owner, I am not sure you would hire on the same axis. I would personally not hire someone that can only work for 20 hours a week, there is too much to do.

whateveracct 6y ago
I've worked at many remote companies by now. None have asked how many hours they're getting out of me. And they all got more or less the amount of time mentioned. And they were all plenty happy with my output! Why would they care if the output was the result of fewer hours? If they wanted to pay me by the hour, they could have negotiated that. At-will salaried employment cuts both ways :) and in this case, everyone is happy. Anyone wanting more hours out of me is just trying to exploit my labor. I'm already getting paid fair value for what I'm producing.
nemothekid 6y ago
>As a business owner, I am not sure you would hire on the same axis If you are hiring salaried individuals on the basis on how many hours they put in a week, then you might be focusing on the wrong metrics. There were plenty of people in tech doing 20 hours of work a week, and spending the remaining 20 hours on hacker news. I bemoan WFH, but not because of work output.
heavyset_go 6y ago
> As a business owner, I am not sure you would hire on the same axis. I would personally not hire someone that can only work for 20 hours a week, there is too much to do. When you're hiring make this known so people can do their own filtering on their end, as well.
- brianwawok 6y ago
  Yup, we make it known. Plenty of companies in the world that you can coast at, it can’t be a company with <5 developers fighting well funded competitors.
  - solosoyokaze 6y ago
    This is only true if you assume 40 hours a week produces better software than 20 hours a week. I’ve not found that to be the case. Software productivity is in large part a function of developer happiness. Plenty of people are happier and more productive with less hours. That’s not even getting into burnout and cost of replacing people.
kasey_junk 6y ago
I get the feeling they were talking about the commute/lunch/break overhead not slagging off for an extra 20 hours per week because they weren’t supervised. I know I get a lot of benefit from not commuting, from being able to make a healthy lunch out of my fridge & from doing laundry when I would have been walking to the coffee shop. If anything I “work” more remote than I ever did in the office.

whateveracct 6y ago

I've worked at many remote companies by now. None have asked how many hours they're getting out of me. And they all got more or less the amount of time mentioned. And they were all plenty happy with my output! Why would they care if the output was the result of fewer hours? If they wanted to pay me by the hour, they could have negotiated that. At-will salaried employment cuts both ways :) and in this case, everyone is happy. Anyone wanting more hours out of me is just trying to exploit my labor. I'm already getting paid fair value for what I'm producing.

nemothekid 6y ago

>As a business owner, I am not sure you would hire on the same axis If you are hiring salaried individuals on the basis on how many hours they put in a week, then you might be focusing on the wrong metrics. There were plenty of people in tech doing 20 hours of work a week, and spending the remaining 20 hours on hacker news. I bemoan WFH, but not because of work output.

heavyset_go 6y ago

> As a business owner, I am not sure you would hire on the same axis. I would personally not hire someone that can only work for 20 hours a week, there is too much to do. When you're hiring make this known so people can do their own filtering on their end, as well.

brianwawok 6y ago
Yup, we make it known. Plenty of companies in the world that you can coast at, it can’t be a company with <5 developers fighting well funded competitors.
- solosoyokaze 6y ago
  This is only true if you assume 40 hours a week produces better software than 20 hours a week. I’ve not found that to be the case. Software productivity is in large part a function of developer happiness. Plenty of people are happier and more productive with less hours. That’s not even getting into burnout and cost of replacing people.

kasey_junk 6y ago

I get the feeling they were talking about the commute/lunch/break overhead not slagging off for an extra 20 hours per week because they weren’t supervised. I know I get a lot of benefit from not commuting, from being able to make a healthy lunch out of my fridge & from doing laundry when I would have been walking to the coffee shop. If anything I “work” more remote than I ever did in the office.