News for hackers. Stuff that matters.

A comment on We Let Our Employee Set Their Own Salaries. Parent comment

Re:We Let Our Employee Set Their Own Salaries by ams6110 on Saturday August 31, 2013 @01:14PM (#6307348)
What's a reasonable workweek then? And why?
[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by malyk on Saturday August 31, 2013 @07:01PM (#6308443)
I know that I have about 5ish hours of good programming work in me a day. I know that I like to take a 45ish minute lunch. I know that I have some admin type stuff to do on occasion.

So, sign me up for a 6 hour day and you'll get my full attention all day. I won't "need" to spend time on HN or twitter or whatever to kill time because I'll be fresh enough to work all day.

Also, because i believe there is a hell of a lot more to life than work, we'll work 4 days a week.

A guy can dream, can't he?

[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by saraid216 on Saturday August 31, 2013 @09:17PM (#6308721)
I wish we were more actively working towards such a world. Instead, we keep getting caught up in political discussions about how people who don't work are lazy.
[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by Ellahn on Saturday August 31, 2013 @01:29PM (#6307396)
Depends on who is working, what they're working with etc.

After about 7 hours of coding, I feel my code starts slipping off. Also, I code better at night. I know people who can't code for more than 6 hours a day or their work gets shitty.

I usually code 6 to 7 hours a day, and I take my friday afternoon (or part of it) and night off. This sometimes means working just the morning and the first half of the afternoon, and sometimes means working until 4am on the Thursday and then not working at all on Friday.

I think when you have great people on your team, that love their work (Not their jobs. Their work), it gets eaasier. This people will do their best, and that can't be measured in hours. That's why a fixed schedule actually sucks and many, many people don't like it.

[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by jevinskie on Saturday August 31, 2013 @05:13PM (#6308114)
Do you not have an hour of "administrative" or "meeting" work to get you to at least 8 hours? I find that my non-coding overhead is easily an hour a day.
[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by zerr on Sunday September 01, 2013 @07:44AM (#6309952)
It originated from: 8 hours sleep, 8 hours work, 8 hours recreation.

But if you add a preparation, commute, lunch-time, etc... you easily end up with only 4-5 hours of "recreation".

Now imagine you have a wife, kids, friends, side projects, maybe want to watch SICP lectures, learn some Haskell...

4-5 hours is simply not enough.

[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by ry0ohki on Sunday September 01, 2013 @02:28PM (#6311463)
It actually originated from shift work. It used to be two 12-hour shifts, and then Carnegie and others realized three 8-hour shifts were more productive.
[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by zerr on Monday September 02, 2013 @03:44AM (#6313946)
Right.

http://en.wikipedia.org/wiki/Eight-hour_day

So after 100-110 years, maybe it's time to come up with even more efficient work day? (But keeping the right direction).

[ Parent | on HN ]
Re:We Let Our Employee Set Their Own Salaries by iopq on Sunday September 01, 2013 @03:50AM (#6309459)
4 hours of actual programming per day, but there's overhead and like lunch
[ Parent | on HN ]