3 ms·

> ...it's very rare for me to have a fully productive day. If I moved to 6 hours per day, I'm not even sure if I'd become less productive, I'd probably just spe

> ...it's very rare for me to have a fully productive day. If I moved to 6 hours per day, I'm not even sure if I'd become less productive, I'd probably just spend less time chatting at the coffee room, and have a smaller chance to get burnout. I'm not sure I follow here. You want 75% of the salary to do the same amount of work? That doesn't really make sense to me. You also have to take into account that companies have to manage the overhead of having more employees (more mouths to feed at events, more HR costs, at certain thresholds it triggers new legal requirements for the business). I doubt you're going to find a lot of takers from either employees or employers. It sounds like you're dealing with a personal issue, which is that you feel like your company is "try[ing] to squeeze all the possible juice" from you. This sounds like you're burned out on your job. Maybe it's time to find a new company, a new position, a new work environment, something that will make you happier than you are now. I'm not sure that less hours and less pay is necessarily the problem here.

aninhumer 10y ago
>I'm not sure I follow here. You want 75% of the salary to do the same amount of work? That doesn't really make sense to me. They want 75% of the salary to do the same amount of work... and then go home.
- rycfan 10y ago
  If you deliver the same value to the company in 6 hours as you do in 8, then you should get paid 100% of your salary. You (should) be paid to deliver "X" value. Auto mechanics have this figured out -- we (developers) should be able to as well. They get paid a certain amount for a certain job (say, 3 hours for a brake job on a certain model of car). If they can do it faster/more efficiently, they still get paid the same amount even if they work fewer hours.
  - Retra 10y ago
    The problem with this idea is that programmers generally never do anything 'correctly', so if you go home early, you're leaving the job unfinished. This is far less applicable to an auto mechanic who simply has to replace a part with another stock part and let a customer walk away with it the same day.
    - bbcbasic 10y ago
      There is some truth in this. Programmers are generallynever finished. You can always refactor or polish it a bit or squeeze in another feature. That said in agile you have a definition of done so at least you can agree as a team when the job is done and then it's like the car mechanic example

aninhumer 10y ago

>I'm not sure I follow here. You want 75% of the salary to do the same amount of work? That doesn't really make sense to me. They want 75% of the salary to do the same amount of work... and then go home.

rycfan 10y ago
If you deliver the same value to the company in 6 hours as you do in 8, then you should get paid 100% of your salary. You (should) be paid to deliver "X" value. Auto mechanics have this figured out -- we (developers) should be able to as well. They get paid a certain amount for a certain job (say, 3 hours for a brake job on a certain model of car). If they can do it faster/more efficiently, they still get paid the same amount even if they work fewer hours.
- Retra 10y ago
  The problem with this idea is that programmers generally never do anything 'correctly', so if you go home early, you're leaving the job unfinished. This is far less applicable to an auto mechanic who simply has to replace a part with another stock part and let a customer walk away with it the same day.
  - bbcbasic 10y ago
    There is some truth in this. Programmers are generallynever finished. You can always refactor or polish it a bit or squeeze in another feature. That said in agile you have a definition of done so at least you can agree as a team when the job is done and then it's like the car mechanic example