5 ms·
I'd be careful with this: this "democratic" budgeting has a similar feeling to "democratic" scheduling--that situation where you tell people to work "whatever h
by derefr 13y ago
I'd be careful with this: this "democratic" budgeting has a similar feeling to "democratic" scheduling--that situation where you tell people to work "whatever hours they like." Everyone sees everyone else putting in extra hours "for the good of the team", and so you get a team slowly whipping itself into a death-march no one actually wants or needs, and resenting anyone who tries to just stick to the (healthy!) 9-to-5. Similarly, in this situation, I'd strongly bet on there being a ratchet effect, where salaries are voted down in tough times, but not voted back up in good times.
- kintamanimatt 13y agoThat's easily solvable. Make the instruction, "Work whatever hours you like with a cap of x hours. Cap cannot be exceeded unless exceptional circumstances happen."
- andrewljohnson 13y agoExcept some employees work long hours and love it. Those are often your best guys.
- jebblue 13y agoFor how long? When do they burn out? What happens when they burn out? What happens to the team, project, product, company, customers, their families?
- richardlblair 13y agoThose aren't necessarily your best guys. Those guys might have to work more because they are spending too much time messing around, and not being productive. Personally I like to give it as much as a can for a solid, honest, 8 hours and call it a day. This way I can give it my all everyday, and still get the R&R I require.
- StavrosK 13y agoI don't think there's much correlation between how much someone works and how good they are. I like to think I'm pretty good, and I work 8 hours a day, and some of my coworkers are also great and work more than that. I generally value my work/life balance a lot and really don't like exceeding 8 hours a day/40 hours a week (and can feel my productivity drop after roughly those amounts of continuous work), but this is probably mostly a personal matter. I don't let other people's working longer hours than me affect me, though, because I know that my total productivity would decrease if I worked longer hours. If that's not the case for other people, or if they like work so much that they want to do more of it, or if they are bored in the evenings/weekends and want to dabble in something, that's great for them. I think the factor that helps is that I don't have management that will say "yeah, but X worked 60 hours a week and you didn't", but I'm pretty up-front about that anyway, and just stand my ground. All that having been said, I do find the US work ethic a bit crazy. Working crazy hours isn't good, and the amount of hours worked per week isn't usually proportional to productivity.
- strictfp 13y agoOr they work best alone and seek their solitude off normal work hours, producing code with no shared ownership, effectively creating a liability for your company.
- count 13y agoTo be fair: they did just ratchet up in a good time. They've not been given the opportunity to cycle down/up though, to your point.
- thomaslangston 13y agoLike most democratic systems, checks and balances are probably useful. I would expect the CEO (or relevant manager) to veto a salary that was unhealthy for the company. It was implied as much when the author indicated that he checked the company's numbers before telling the team the average salary would be used. Also, the very transparent nature of the company's finances in this example also helps a democratic process work smoothly.
- Chris_Ashworth 13y agoThat inference is correct: I reserved the right to veto if it was wildly over our budget.
- zerr 13y agoIn the long run, 9-to-5 is terribly unhealthy as well. I wonder when we get rid of this 40 [or more] hr/week stigma.
- ams6110 13y agoWhat's a reasonable workweek then? And why?
- Ellahn 13y agoDepends 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.
- jevinskie 13y agoDo 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.
- malyk 13y agoI 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?
- deleted 13y ago[deleted]
- kristopolous 13y agoI do 20 hours a week, at most. The "work what you like" in the hands of someone who sincerely thinks "fuck work" actually seems to work as intended.