6 ms·
If you're getting your work done, on time, and to the quality specifications, who the hell cares how many hours in the week you work? We're working on computer
by falcolas 12y ago
If you're getting your work done, on time, and to the quality specifications, who the hell cares how many hours in the week you work?
We're working on computers, doing work which does not benefit from typing for N hours straight; there is no meaningful correlation between quality/quantity and hours worked.
I wish more people realized this.
- viame 12y agoIt really depends from whose perspective you're looking at. If you are working for a startup this is exactly how you may think. If I am the owner I would probably think otherwise. There is always more work and more responsibilities that someone can take on, and I would expect my people to do just that. If you're doing something specific in half the time it normally takes, it doesn't mean you can't start doing something outside of your scope and expend your knowledge, maybe help others with their work.
- falcolas 12y ago> If I am the owner I would probably think otherwise. If you're the owner, you're the one setting the goals and timelines. If your team seems to easily meet your expectations, then yeah, you're justified in pushing them a bit. But if they can't keep up, you have to make the choice between hiring more people or easing the expectations back to where your existing team can complete the tasks. There is a third option: push harder and expect more from your workers, but the tradeoffs from the short term productivity increase is just that - short term - and detrimental to your business in the long run. More specifically, if person A can get `N/2` tasks done in a week (where N is the average velocity), and person B can get `N * 2`, reward person B, set up a performance plan for person A, assign out tasks appropriately, and move on with life. If you really need `N * 5` output every week and have four employees, hire another employee. Don't keep giving person A N tasks and expect persons B, C, and D to do their work plus person A's. EDIT: Formatting fix
- commondream 12y agoOr where you work from. Most of our dev/design team is remote, and that's been hugely beneficial to us. I wish we could figure out how to shoot really high quality video remotely too.
- mistermann 12y ago> We're working on computers, doing work which does not benefit from typing for N hours straight; there is no meaningful correlation between quality/quantity and hours worked. Has it genuinely been studied in a meaningful way, and this was in fact the conclusion?
- falcolas 12y agoI recommend visiting the question and answer found here and make that decision for yourself: http://skeptics.stackexchange.com/questions/14028/does-working-over-40-hours-a-week-makes-you-less-productive http://skeptics.stackexchange.com/questions/14028/does-worki... For myself, it's absolutely the truth. I do not get more meaningful work done in 8 hours than I do in 6, or some days, 1. I spend more time thinking about design and implementation than I do coding, and thinking does not require me to be at my computer, or even in the office. The only benefit of being in the office is the ability to BS with my colleagues (and occasionally it's even about work!).
- 31reasons 12y agoBut here is what goes through the mind of a manager who never been a programmer: If John is working only 4 hours coding everyday and gets stuff done. He can do double in 8 hours. So I should ask John to not goof around and focus on getting more things done.
- sopooneo 12y agoAnd while there are severely diminishing returns on more hours worked, there is of course an optimum. Most of us will get more done working five hours a day then five minutes. So the challenge seems to be finding the ideal and somehow getting management to understand/believe it.
- falcolas 12y agoI think the challenge there is that the "optimum" varies from day to day. Some days, John might not need to be in the office for more than 5 minutes - the time to check and respond to emails - and other days he might need to be in there 12 hours as he dumps the contents of his brain into an implementation.
- socialist_coder 12y agoYou don't hire those managers in a company that values 4 day work weeks.
- weisser 12y agoNon-technical co-founders need to avoid this way of thinking too. It's detrimental to the personal relationship and any potential for a positive outcome.
- IndianAstronaut 12y agoI have a technical boss now whereas before I had a non technical one. My previous boss would have me stay till 10 or 11 sometimes. My new boss lets me go home and take naps in the middle of the day. My productivity has been roughly the same at both places.
- commondream 12y ago
- sopooneo 12y agoLet me play slight devil's advocate. I am a coder that is now starting to take on some management tasks. How much work should I ask people to do? Because it's even harder for me to guess how long something should take a programmer than it is for them to guess themselves. So if we assume that all the programmers are honest (which I do), then I can't just say "get this done by Friday." But I can say, "So you think this might take a week? Okay, I know how hard it is to do estimates, so please make your best effort to reach that goal, but if problems crop up, let me know and we'll adjust the schedule. Or if it turns out to be easier than you thought, let me know that too, and we can find another fitting task for you to tackle." Regardless, it only seems possible to ask a certain amount of time and effort from a programmer since that is the basis on which the schedule is created. Now I fully acknowledge the ideal amount of time is likely less than 40 hours a week. But still, it's the most a person can comfortably get done in a certain amount of time that we're paying for. How else could it work? I fully acknowledge there may be better alternatives, and I'm glad to read about them. My only caveat is that such suggestions would be best if realistically applicable to full-time employees, which is short-term-unchangeable situation I'm in.
- jghn 12y agoAs long as you all aren't consistently incorrect in the same direction it'll probably work out. Suppose week 1 you tell me to get X done by Friday and I finish on Thursday. Perhaps I get Friday off, slack off or whatever. Then on week 2 you tell me to get Y done by Friday and on Weds I realize that's not happening so I end up working an extra 8 hours over thurs and fri to make it happen. What's the difference? (Yes, I realize that this is an overly simplistic example, but hopefully it conveys the point)
- sopooneo 12y agoIf things average out on week (or even month) level, then I think you are absolutely right. So far they pretty much have for me. In full disclosure, my job is effectively lead developer right now, and I am officially "manager" for only one junior level programmer. Who's been awesome so far, and my push with her has been mostly making sure she leaves on time as I worry she's working too hard.
- samspot 12y ago> If you're getting your work done, on time, and to the quality specifications... Does this exist in software development? There is always more work to do than there are people to do it (wherever I have worked). If I clearly goof off/don't work friday while others struggle to push us to our goals, I will not have a very good relationship with my team. Our team philosophy is that if you finish early, then you help others out who are struggling. I'm all for working less hours, but there would have to be a perfect storm of events to make it a regular thing, including a push from management to make it the culture. I don't think it's fair to blame this on bean-counting or crazy managers. Many of us are salaried and don't have people scrutinizing our hours worked.
- jforman 12y agoThis can be addressed by managers making more reasonably attainable goals. Every other industry in the world has an endless list of things to do as well and yet most don't suffer from the same lack of work/life balance.
- jghn 12y agoAt least at my work there's always more to do but that doesn't mean it's always worth jumping in on it. For instance I tend to be put on larger umbrella tasks which take a few weeks. It isn't uncommon for me to wrap up a little ahead of time - sure there are things I could do but usually because of the way things have been planned there are other pieces of that puzzle which aren't fully in place either. So I'll poke around a bit but take it easy for that day or so. Sure, I could jump in to help someone else out for that day but is it really worth distracting that person to get me up to speed with what they need and what they're doing for what would amount to a few hours worth of work? Not really. The flip side of this is that when one finds themselves in a position where the deadline is going to be difficult to meet there's an expectation that extra time is put in to make it happen. As long as the two are happening roughly the same it balances out anyways.
- morgante 12y agoThat's basically what makes agile (in the original iteration) so valuable. Give engineers the discretion to take on what they deem reasonable and trust them to finish it.
- overgard 12y agoI think the problem is that in your average job, the company is paying you for your time, not your productivity. I mean they should be paying you for your productivity, but that's pretty hard to measure and easy to game. I think it does have an unfortunate cooling effect though, in that, if they're paying you for your time there's no particular reason to put in extra effort to do things faster or better (other than personal pride and the nebulous possibility of a raise somewhere down the line). There's been times I've gotten my entire sprint done in a couple days, only to get rewarded with... more stuff to do. That's not a criticism, I mean, that's the employment agreement I signed up for, I'm expected to do stuff 5 days a week, but I imagine that if I could get a sprint done in 3 days and then take 2 days off, I would be more motivated to get that stuff done quickly, and then QA would have more time to test it, and so on.
- vacri 12y agoWhich highlights another issue - when problems are found in what the dev has 'finished', where is the dev to talk it over or rework? It's like the good old "Don't push on a Friday", except now "Friday" can be Wednesday or Thursday. I imagine that there'd be more than a few of the less scrupulous devs who would push stuff earlier than they should (which creates more work for everyone downstream), to get the promised day off. In any case, if you do find yourself with extra days left-over in your sprint, why not tackle some tech debt or documentation, things that are usually lacking?
- bdowling 12y agoIf you are hired as a full-time, salaried employee of a company, the default expectation is that the company is trying to buy ALL of your professional output. They expect that you treat your position not just as a job where you work so many hours or do just the tasks that you are asked to do, but that you take more personal responsibility for doing the very best job you can, improving your own productivity, and making the company function better and more efficiently. Your work for the company is not just a job, it is a part of your career. You're not just an hourly assembly line worker, you're part of the team, an insider, and remember, "We're all in this together." The company managers don't care about you and your work/life balance, only the work they can get out of you. And in terms of efficiency, that means paying you the smallest salary and benefits that you'll accept. And it means telling you whatever is necessary to get you to be as productive as possible. If they can get you to inprove processes or something, even better. Also, with pretty much everything in life, including software development, there IS a correlation between hours worked and quality/quantity. All other things being equal, the one who spends 40 hours working, not just typing, but thinking about the problem, fixing bugs, finding new ones, improving performance, refactoring to improve structure, et cetera, will produce work output that is higher quality or in grater quantity than the one who puts in 30 hours. And I know you're the special snowflake who can do a better job in 30 hours than that other guy can in 40, but that's irrelevant. They are paying you a complete salary, so they can demand that you put in complete effort. The good news is that once you can prove that you're producing more in your 40 hours than the other guy is, you can demand a higher salary or take your talents elsewhere. Edit: Fixed grammatical error.
- larrys 12y ago"Special snowflake" actually describes quite well stories like the OP which totally are not representative of how the world actually works for 99% out there. Most people have to work very hard much of the time and as a general rule it pays off. [1] Nobody that you have ever read about and for that matter all the people that I have ever met that nobody has ever read about have gotten there working a short schedule. Exceptions? Sure. This nonsense has to end. Unless someone has for some reason hit the tech startup lottery, work hard, as much as you can. You won't always (when you are older) be able to do so. By the I knew Arrington (mentioned in the article) prior to Tech Crunch. He worked very hard to try and convince me to join Pool.com writing multiple times and not taking no for an answer. Back and forth, negotiating all of that. And I'm glad he did because after agreeing to get involved we made a ton of money from that service for years. I owe that all to the effort that Mike put in and was able to do so because of the hours that he worked (as well as the hours that I worked which was "all the time".) [1] The problem is people don't realize that some people can work all the time, actually enjoy it and not be stressed. Just like some people can exercise or can climb mountains or swim fast or practice piano or anything else. Just because it burns one person out to work 7 days don't assume that it burns everyone else out to do the same. If you are exceeding your limitations and can't take it don't assume that everyone feels the same way (although they might..)
- cpprototypes 12y agoI think the best balance is to allow remote working anytime, but only hire local. The focus of management should be on results, not on hours in the office. This system has the best of both worlds. Remote from anywhere in the world has a lot of issues. The benefits are well known. Time flexibility and it forces management to focus only on results. However, doing face to face meetings is extremely difficult due to distance. Even tools like skype and hangouts are not effective when big time zone differences exist. Face to face communication has a lot of advantages and it's missing in this kind of workplace. Forcing everyone to be in the office everyday also has a lot of issues. Going to the office and staying 8 hours or more regardless of productivity is a waste of time. There is also the wasted time commuting and it allows management to be lazy by focusing on hours in the office instead of actual results. Allowing remote anytime anywhere, but hiring only within 50 miles of the office has the advantages of both. Face to face meetings are easy to schedule since everyone is only 50 miles away or less from the office. There are no time zone issues so skype and hangouts are very effective. It also allows all the flexibility of working remote.
- a3voices 12y agoI like to always physically going to work because then the environment externally pressures me to actually do stuff. I much prefer the external pressure instead of internally trying to motivate myself.
- jmccree 12y agoI feel like widely distributed teams have a whole different set of problems than remote in the same time zone.
- jdmichal 12y ago> If you're getting your work done, on time, and to the quality specifications, who the hell cares how many hours in the week you work? This is a simple question with a very simple answer: Because if you can get your work done in 15 hours, that means you can handle more work. I can't think of a single project I've ever worked at where there wasn't bugs or backlog or refactors that I could work on during spare moments. What kind of place do you imagine working for that doesn't have these waiting to fill in time?