28 ms·
At some startups, Friday is so casual that it’s not even a workday
- falcolas 12y agoIf 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?
- unimportant 12y agoSome startups are so casual, that work is not considered work and more of a paid hobby, with unpaid overtime being insisted upon...
- not_a_test_user 12y agoI can't believe how negative the article's comments are. Is everyone so addicted to work? I would understand if I could work at top performance 10-12 hours a day, 5 days a week but that's just not possible for me. In the end driving developers to exhaustion is worse for everyone, with subpar code that'll probably require refactoring Monday morning.
- Disruptive_Dave 12y agoYes, everyone is addicted to work. This is what we've been conditioned to know/believe/live. I'd also venture to say "fear" is the foundation upon which many managers/motivators operate, at least here in the U.S. Remote work has the same challenges; "if I can't see my employee at his desk, he's probably screwing off somewhere!". It's lazy, but it's what most know.
- fsloth 12y ago"Remote work has the same challenges; "if I can't see my employee at his desk, he's probably screwing off somewhere!" This should not be a problem in a sane software development shop because there should be a way to track a) code reviews done b) tickets implemented/code merged /etc. LOC/hour is a crappy metric for software development but averaging these over, say, six months should give some indication if someone is slacking off. Or just working in a different project than anyone else but task based variances ahould be accounted for. It does not give a "perfect metric" that could be used for perf evaluation but should be a sufficient safe guard against total slackers.
- zaroth 12y agoI wonder if they pay part-time salaries to reflect the work hours. Certainly an interesting trade-off. If you have kids and a stay-at-home spouse I can certainly understand the appeal! Otherwise, perhaps not so much...
- nfriedly 12y agoI interviewed with Treehouse a while back, and from what I recall, they were a little below market (for an experienced remote dev) but not outrageously so. I would have been willing to accept the pay given the hours and other aspects of the job, but we didn't work out for other reasons.
- commondream 12y agoWe come pretty average for the U.S. but under SV pay. We don't cut pay to adjust for the shorter week, though.
- k-mcgrady 12y ago>> "I wonder if they pay part-time salaries to reflect the work hours." It's only 8 hours less than the average work week so I'd expect the salary cut to be minimal.
- jqm 12y agoWould you consider 20% minimal? because that's the hours from a 40 hour week that are cut.
- k-mcgrady 12y agoTrue but if they are actually productive in those 32 hours it could work out the same. How many hours per day do startup guys waste playing ping pong and browsing HN? Maybe if they have the Friday off they would procrastinate less during the 32 hours and output would be the same. Personally I think a shorter work day would be more effective than a full day off as regards to productivity. Also, look at the number of companies that do/have done 20% time. If giving employees 20% of the week to do whatever makes them happy result in better productivity it would be fair to keep the salary the same.
- cubano 12y agoWasn't there a thread recently here that discussed how everyone was expected to work 60-hour weeks by their managers or face heaps of wraith? So what is it...32 or 60? The only answer can be "it shouldn't matter!", if you work in an industry where you can just as easily work from home as work from your desk. I am speculating, but I would think that most of the IT developers at Treehouse work well over 40 hours a week.
- copsarebastards 12y ago> The only answer can be "it shouldn't matter!", if you work in an industry where you can just as easily work from home as work from your desk. Huh? How many hours I work has very little to do with whether I can work from home. If I'm expected to work 60 hours/week and have the option of working from home for all of them, that's definitely still a problem.
- nothrabannosir 12y agoHe means that working from home implies quantity of work is less important than quality. Nobody knows how much time you put in, but yourself. One way or another, you will be judged on what you deliver, not how much time it took you. Some managers (or even people hiring contractors) think they can get around this, but, ultimately, you can always do in 4h what they expect you to do in 8h and get paid for 8h. Not saying it's moral, but it is the reality. The conclusion is inescapable: working from home implies that the only important metric is the quality of your work (and the deadline), not how much time you spend on it. Because you can "simulate" one with the other. Some people don't realize this, yet. Doesn't make it not true. EDIT: PS: I'm talking about project where the "deadlines" are reasonably far apart and predictable. Say, no more than a few times a day. If your work includes being on-call and responding to incoming requests, that's a different story.
- copsarebastards 12y ago> Some managers (or even people hiring contractors) think they can get around this, but, ultimately, you can always do in 4h what they expect you to do in 8h and get paid for 8h. I can do that, but I won't. I value my integrity. So to me, it definitely does matter if I'm expected to work 8h as opposed to 4h, even if I can work from home.
- heynk 12y agoAt my last job and now at my current job, I negotiated from full time work to less than full time work. Last time, I didn't work Fridays and now I work 20 hour weeks. In each case, I am absolutely more productive (per hour) that I honestly don't know if I get any less work done. On top of that, I have much more creativity and energy. From this experience, I'm always on the side of pushing for less work hours per week as a standard.
- ThrustVectoring 12y agoI know that I have roughly 5-6 hours worth of productive programming time in any given day. If I had a job where I was required to be on-site for eight hours a day, I'd get roughly the same amount of work done. Maybe even less, since I'd practice sitting at my work desk not doing things for 2-3 hours per day. I'm a huge fan of the whole "notice you're not accomplishing much -> go home" plan.
- monsterix 12y agoNow this could be an early sign of a bubble in the making. Here's why: 1. The bay believes that solofounders are a bad deal - mostly - because starting a company is a lot of work. And so it is - a lot of work! 2. Now here we have a handful of _startups_ that confess there's isn't enough work to keep everyone in the nimble team up on toes for even forty hours a week! This contradicts with 1. Sure it means team happiness and all that. Fine. 3. For each _startup_ that has confessed situation at 2. there should be at least 'X' times the number of start_ups who do not accept this reality. I don't know what that number 'X' would be but let's take it 10. Which means what - a bubble? [Left open]
- divegeek 12y ago> here we have a handful of _startups_ that confess there's isn't enough work to keep everyone in the nimble team up on toes for even forty hours a week I don't think they said anything of the sort. There's no claim they don't have enough work for 40 hours; I'm sure like most of us there is no end to the work, and it can and will consume all the time we're willing to give it. They're just not willing to give it as much. It's possible that will put them at a disadvantage to their competitors. It's also possible that they may be sufficiently more creative to overcome that disadvantage.
- monsterix 12y agoYeah, but negative vote is a perfect example of how stupid this community has become. Not even able to digest even the slightest counter-thinking, and the recoil is never short of abusive. Look at the moron below who calls "up on toes" as corporate slang. NO. It's not a corporate slang, rather a pursuit of a start_up to beat the rest. Hopeless! This site used to be quality. Now it's full of sheep with one-track mind. My last note here. Go ahead vote it down, enjoy your dumb echo-chamber and live through your satisfaction. Bye.
- iopq 12y agoYou got downvoted because your post doesn't make sense.
- itbeho 12y agoInteresting how the companies discussed are outside of SV.
- commondream 12y agoI think there have been pros and cons of us being outside of SV. I'm personally really glad that we're not there. I love Portland and think it's been a really good place for my family. I know we have folks who wish we were more present there too.
- beat 12y agoI'm in Silicon Valley right now for conferences (SaaStr and Startup Grind), enjoying soaking up the culture, but I've had at least a half-dozen people advise me to move here. No, no, no! As much as I love it here, and as useful as it is for business, I'd rather live in Minnesota.
- beat 12y agoSilicon Valley's startup culture is eerily reminiscent of 19th century Europe... "We're more successful than everyone else, so our culture must be superior to everyone else's culture." This completely discounts all the other factors that led to localized success. Silicon Valley is a successful environment for startups because it has many unique advantages that have nothing to do with working harder - see pg's numerous essays on the subject. "Hard work" (defined as long hours and obsessive focus) is not the key ingredient, because people work hard everywhere. I watch people do startup-like hours in the sluggish old enterprises that baffle startup folks. Concentration of money and experience? That matters. Think about the utility function of hours worked. What's the relative productivity of the 50th hour of work this week, compared to the 10th? At what point does exhaustion and overfocus actually hurt rather than help productivity? It may be earlier than you think. If I'm only 20% as productive on the least pleasant working hours, why am I even doing that to myself and the people who love me? Work is a marathon, not a sprint. If you sprint in the middle of a marathon, you'll get a slower time overall, because you're draining too much energy. Likewise, an all-nighter or two of coding will hurt you for days afterward. Work smarter, not harder. People who brag about how smart they are should understand this.
- bdcravens 12y agoI really don't get much "work" done in the office; most of my work gets done at 2am or on the weekends. (We talk alot and strategize, so technically that's work I suppose, but the actual coding usually happens elsewhere)
- AndrewKemendo 12y agoMy question is, what do you tell customers that demand responses Friday through Sunday? I mean if something breaks I am sure people come in/do remote work, so that's not the cases I am talking about. I assume this only works for companies that have non-critical or fully automated products where users don't have any person to person interaction built in anywhere. I ask because I would love to implement something like this, but we get requests for service or user questions every day - and a three day turn around time on a user issue is terrible customer support - especially if they have other work riding on it. I realize treehouse is different in this respect. It seems like the more employee focused you are the less responsive to customers you can be.
- commondream 12y agoWe have a support person who works his four days over the weekend to make sure it's covered.
- AndrewKemendo 12y agoSounds like lonely work. Sacrificing one for the tribe! We did this in the military and would rotate who had Watch/CQ/duty[1]... [1]http://terminallance.com/2013/08/15/terminal-lance-286-duty-ii/ http://terminallance.com/2013/08/15/terminal-lance-286-duty-...
- commondream 12y agoHe works on Mondays with the team to help with that aspect, but yes, it'll be great when we've got two weekend support folks.
- mt3ck 12y agoNot always so.. maybe his circumstances favor working on the weekends and it happens to be a benefit to him?
- deleted 12y ago[deleted]
- vjeux 12y ago> These days, on Fridays, he gets his two young sons off to school and spends the day hanging out with his wife, Gill. “It’s like dating again. We go to coffee shops. We read books together. I really feel like I’m involved in my kids’ lives and my wife’s life,” This assumes that your wife is not working. I've tried taking some days off like this and, in the middle of the week everyone works, so you don't get to hang out much
- commondream 12y agoYeah, my wife's back in school, so we go to lunch but beyond that we don't get to spend our whole Fridays together. When we were getting started Ryan would go on adventures with his family on Fridays, but my kids were already in school. YMMV on the family aspects of having Fridays off. But I'm no martyr. If you think Friday with your family is awesome, you should try having Fridays with almost no responsibility sometime. It's pretty great.
- socialist_coder 12y agoFor me, the biggest thing about having Fridays off is you actually get a day for yourself. My weekend is 100% spent with my wife and kids, so having a Friday where I actually get to unwind and do my own thing (hacking on Arduino, playing games, programming for fun, whatever) is crucial to my well being. Before I had kids, this wouldn't have mattered since you already have 2 days a week you can do whatever you want. Having 3 free days a week vs 2 is not really that different. But after kids, and working 5 days a week, I had 0 free days a week for myself. Going from 0 to 1 free days a week is a HUGE difference.
- epberry 12y ago"...as a thunder lizard, the tech world’s name for the tiny handful of start-ups that actually become $1 billion businesses." I thought we were calling these unicorns? Maybe I'm behind the times terminology wise.
- commondream 12y agoI thought unicorns were people who can do anything. I'd never heard the thunder lizard thing either, though.
- pluma 12y agoIn web development at least, unicorn generally refers to developers/designers who are very good at both. Not sure how the term is used outside of that context.
- terravion 12y agoNo, you're not behind, it doesn't seem that anyone on this thread has heard of a thunder lizard. I wouldn't trust the Washington Post to have this kind of tidbit right either.
- commondream 12y agoI'm Treehouse's CTO and cofounder. I'll try to answer anything I can.
- lacker 12y agoHow large have you gotten with no managers?
- commondream 12y agoWe're a little above 80 people on the team.
- throwaway1184 12y agoWhat's the optimal amount for "computer people" to work each day, in your experience? What percent of "working time" do you think consists of actual "work"? Do you have any opinions about optimal work spaces?
- commondream 12y ago> What's the optimal amount for "computer people" to work each day, in your experience? I think a lot of folks, once breaks and all are accounted for, probably work 6-7 hours in an 8 hour chunk, and that seems to work pretty well. > What percent of "working time" do you think consists of actual "work"? See above :) > Do you have any opinions about optimal work spaces? I like a clean desk. I like to stand more than I sit. I like to be in a spot where I can walk freely, and I go outside a good bit during the day, even in our lovely Portland rain, to think. I think the best work space is probably always the one you want, and over time what you want changes. It's iterative. We have folks on our team that like working from home. I like working in the office. Some of our team sits on the couch at the office with their computer in their lap, and that seems crazy to me. So yeah, whatever you want.
- throwaway1184 12y agoCool, thanks for the reply. Do you see the "6-7 actual / 8 attempted" thing to be "inevitable", like that's the maximum ratio people can reasonably sustain, or do you think that with better environment and habits, we could/should get up to 8/8? (I'm obviously not talking "eliminate lunch", though. More like "eliminate needless chichat/mindwandering/newsreading")
- woodchuck64 12y agoFatigue is such a killer of creativity and innovation. When I'm tired I feel my brain deliberately shying away from anything but the familiar and rote. How many great ideas have been sacrificed to stay an extra hour at work instead of using that hour for rest and replenishment?
- sreitshamer 12y agoWhen I get really, really tired I get more creative, not less.
- commondream 12y agoIt's a balance though, right? Sometimes I'm still tired at 6AM when I wake up and I have to get out of bed and do things anyway. Then other times I'm tired at 4PM and I just give up and go home. I think you've got to do the work, but being flexible around the margins is great.
- colmvp 12y ago> “As far as I’m concerned, working 32 hours a week is a part-time job,” Arrington, said in an interview. “I look for founders who are really passionate. Who want to work all the time. That shows they care about what they’re doing, and they’re going to be successful.” Efficiency is key, not some arbitrary limit of working hours. Chances are yes, as a founder you aren't going to work just 32 hours a week. But it also depends on the state of the company. And quite frankly, sometimes you can't solve problems by sitting at your computer or even talking to others in the office. Sometimes it involves taking a break and chilling out or exercising.
- xivzgrev 12y agoI've been waiting for an article like this. There really is an ethos of working yourself to death, and on surface it can make sense. If you put in 80 hours per week and your competition puts in 60, you'll win because you'll learn more quickly than your competition. But I don't think that accounts for efficiency. If you work 80 hours per week, is every hour equally productive? And if so, are you working on the most valuable things? (Eg can you delegate, outsource, etc?). People like to think so but it's far from a universally held belief. On the flip side, if you work 32 hrs per week, you're pretty much forced to be focused and productive. You'll still have same goals, how do you achieve them in half the time each week? You cut out things. I just graduated from one of the many bootcamps, and about half of students "worked" about 45 hrs per week, vs other half who worked 60+ hrs. And there's been zero difference thus far on who has gotten jobs more quickly. Ok I'm done with my soapbox but I wish more people in valley would consider worldview espoused in this article. Also with the Michael Arrington comment, I don't think most investors give two shits how long you work as long as you are delivering that up and to the right growth.
- fndrplayer13 12y agoIts good that places like this exist. My experience thus far has shown me that different developers might go through different phases of their careers in terms of how much they like to work. I think the article touches on this a bit, noting that most of these people are married and have families. I'm married, but I still totally feel the urge and drive to work on software all the time. And its not that I love work, its that I love writing software. I could see that drive tailing off with kids and those kinds of deep commitments, though.
- jstoiko 12y agoI feel like some people have built this fantasy that working at startups is like vacations. These people probably work their ass off during their 40, 60, or maybe 80 hrs on the job. So they dont understand when they ear that startups' work schedule is more relax because they cannot relate to it. However, when they leave their desk, it's over, they're up to something else and they probably even force themselves not to think about work anymore. Startups take a relaxing approach to work hours because the (right) person who works there lives and breathes startup 24/7. It's easy to say when you're a founder (disclaimer: I am one). But it is something I have witnessed in (good) startup employees as well. They think about it all the time. @falcolas is right, who the hell cares how many hours in the week you spent executing your tasks? Shouldn't the time "thinking" about work be valued as much as "executing" the work? Don't we all "think" better outside of execution time?
- commondream 12y agoYep. Turning your brain off is impossible, and your brain's the most critical piece of you in a lot of these roles. If we counted thought time I'm not sure how many hours I'd log each week, but it'd be well above 32.
- vram22 12y ago>Turning your brain off is impossible That is what meditation is supposed to help one do - in a sense :) - thinking when you need to, none when you don't.
- commondream 12y agoI retract my statement. Let's pretend I said "Turning off your brain is hard" instead?
- vram22 12y agoGood point.
- raverbashing 12y ago
- rajacombinator 12y agoI love reading about work style experiments like this and think they're great in some situations. But they make more sense for serial founders who have cashed out before or established cash cows like Google/Apple/Facebook. New founders who are all in on a business can't afford to work 4 days a week because the clock is ticking.
- BadassFractal 12y agoYup, that's exactly what I mentioned as well. Nobody who's hungry and trying to break through can afford to slack off and expect massive success.
- ripberge 12y agoTreehouse is actually in a very luxurious position right now. They've raised a bunch of VC and this is a fairly new niche they operate in and more and more of society is recognizing how valuable these skills are. They can work minimal hours, see a lot of growth and everyone is happy. Fast forward five years from now. There are going to be a ton of tough competitors in this space and eking out revenue growth month over month is going to be much harder. However, in five years they probably have the added pressure to start thinking about something called profitability. The going is going to be a day of reckoning here when the harsh realities of cut throat competition set in. That just hasn't happened yet.
- commondream 12y ago> However, in five years they probably have the added pressure to start thinking about something called profitability. We don't talk publicly about finances, but let's just say that's something that's been thought about already and that bit of what you're saying doesn't scare me. > There are going to be a ton of tough competitors in this space and eking out revenue growth month over month is going to be much harder. Codecademy (free), Code School, Pluralsight, Lynda, Udacity, Coursera, Udemy, free online content. Things are already tough, and they get tougher every day. We have an amazing team that works like crazy, 32 hours a week, because we believe we're uniquely situated to work on this problem. So the competition thing won't magically appear. It's already here.
- pi-err 12y agoRefreshing. After a burnout, I set to work 25h a day (program management role). I realized soon enough that I was crazy more efficient. I was also less stressed, less verbose, left all frustration behind, and started to see people change the way they saw me (= they started to like me). It's a competitive advantage to offer less hours and more intensity.
- deleted 12y ago[deleted]
- 12y ago
- blahedo 12y agoTwo things in the article that I found interesting but were not highlighted: > "But he soon found himself working that same intense pace until his wife asked him why he was working more and making less. She suggested taking Fridays off." So the central concept of this workplace format, around which this entire article is based, was the idea/inspiration of Ryan Carson's wife, whose full name is not even mentioned. (Her first name is Gill, but is her last name Carson? Unclear from the article.) Not that it's a purely original idea---other companies have done four-day workweeks before---but it was obviously one that hadn't occurred to this particular founder. Three cheers for Gill possibly-Carson! > "With Treehouse, Carson said he hopes to, again, buck conventional start-up culture, and not cash out by selling the company, the brass ring for most start-ups, but continue to run it as a sustainable business." Let's hope that also starts a trend. I'm so heartily sick of companies building a great product and actively recruiting user bases to use and love that product, only to shutter it and throw all the users under the bus when the founders achieve their real goal, which is getting the attention of Google or Facebook or whoever and getting acquihired or otherwise bought out. I know that individual founders and other startup workers will often (indeed almost always) say that they really do care about their users, but as a collective structural pattern in the way that SV startup culture seems to work, it sure doesn't look that way from afar. So three cheers for (the currently-stated intentions of) Ryan Carson!
- commondream 12y ago> Her first name is Gill, but is her last name Carson Yep, Gill Carson. It does suck that they didn't give her more credit. Gill's had a lot of positive effect on Treehouse.
- k-mcgrady 12y ago>> "whose full name is not even mentioned. (Her first name is Gill, but is her last name Carson? Unclear from the article.)" I think the general assumption when two people are married is that they have the same surname. I know this isn't always this case anymore but it seems to me that it's so common that if her surname was different they should point it out but that it's unnecessary to do so if it's the same.
- iopq 12y ago
- Jemaclus 12y agoBack when I first got into the start-up scene, I used to work long hours because everyone else did. At some point, I realized that literally nothing has to be done RIGHT NOW OH MY GOD RIGHT NOW. Almost everything can wait until tomorrow morning. Sure, there are some high-priority bugs that are breaking the site that need to be fixed ASAP, but during normal operating procedures, once that clock hits 5pm, I should start wrapping up my work so that I can pick it up fresh in the morning. I don't take my work home with me, I don't check my work email when I'm at home. It's just not worth the stress to me. I love my job, I love my work, I feel like I'm contributing to making the world a better place -- it's just not 100% of who I am. I have a dog, a girlfriend, a handful of close friends, a few engaging hobbies, and a ton of books to read and miles to run. I'm more than my job, and once I can pay the bills, the rest of the money is just a nice to have -- but not nice enough to give up my health and sanity. Then again, I'm extremely lucky to be in this situation, and a lot of people aren't. Some of my coworkers work long hours still, but they seem happy about it. As long as that's true,... well, whatever floats your boat, right?
- dasil003 12y agoI'm not sure if it's due to increased self-awareness, or whether it's physically due to aging, but I know for a fact that pushing over 50 hours a week will quickly lead to lower overall productivity for me. I love what I do and I used to work insane startup-level hours, but on reflection a lot of those hours are less efficient, whether due to decreased efficiency or downright procrastination when I'm too tired to deal with a difficult problem. To some extent I think tech startup culture evolved this way not just because it takes a superhuman effort to build a successful company, but also because learning to be a good programmer is something that is extremely difficult if you're not at least a little obsessed with it. My tendency to work 80 hours a week at my startup is the natural evolution of my 14-year-old self wanting to spend all my time working on the computer. But now that I have a couple decades experience under my belt, I can sit down and focus for 8 hours that will lead to far more productivity than slogging through 16 hours. Furthermore, my subconscious is able to continue working on problems during my downtime, so stepping away, getting some exercise, cooking some healthy food, sleeping 9 hours all feed back to greater overall productivity.
- arturnt 12y agoAn average work day isn't filled with 100% development. You have breaks for lunch, coffee, people asking you questions, meetings, ping pong, etc. For a good workplace a chunk of your time is a social experience like any other. That means if you spend about 2-3 hours a day total socializing, then the 5 hours a day you spend working. For startups, sometimes you have time sensitive releases so that number goes from 5 to 10, but it's still only about 50 hours of actual development per week even though it's 65 with all the other stuff included. Treehouse has managed to make a 4 hour week work since everyone is working remotely, so that social aspect is not as prominent and consumes less time. For people who have kids spending time for the kids becomes more important than the social experience at work as it should. The 4 day work week all of a sudden makes sense since they have bundled those 3 hours / day of a work social time into one day of a kids time.
- varunjuice 12y agoThis is just recognition of the fact that productivity is divorced from # of hours at the office, or # of hours spend "working'
- spiritplumber 12y agoWe work five days a week, one of which is shared so we can talk. Which five days is up to the person. Of course since I'm a cofounder I work pretty much 24/7 but such is life...
- stillsut 12y agoPretty simple: if a developer can be 10x-100x as productive than the average developer, you don't really worry about only getting 80% of their required time. So if this perk gets Treehouse talent that is +30% more productive, even if they lose -20% of productivity from Fridays off, they still win. One caveat, so much of programming is loading things into your head, I think three days off every week would be difficult for anything sophisticated being developed.
- sandworm 12y agoIn my work (legal) i often find myself overdressed and overstressed about decorum and timetables. But corporate decorum, working 9-5 m-f, has a place. I remember one incident where a thursday meeting at a startup was canceled because a department head wanted to turn an already long weekend into a 4day holiday. I put my foot down. Fridays are not weekends. If they are, then thursdays become fridays and you'll start skipping them too. That meeting consisted of me in a suit, in an empty office, talking to two people via skype. I call that a victory because the meeting at least happened. (The truth is that all the low level employees on the first floor were there and working. They cannot afford to skip out on work.) Casual is all well and good until it creates unpredictability and disorder. Contrary to popular myth, things actually get done in meetings. Not every decision can be made while scaling the in-office climbing wall. Some decisions require people sitting down at a table to hammer through a series of points. Does that thing that happened last night on the server qualify as a breech? I don't care that tomorrow is a friday. Neither will your backers, nor the FBI, when they haul you in to explain why you couldn't be bothered to take a decision until after your ski weekend.
- free2rhyme214 12y agoThis is a nice way for Treehouse to differentiate itself for talent but this is blown out of proportion like Tim Ferris's 4 Hour Work Week. Employee culture is important but to be honest I only care about how well the founders are executing their original vision then all the yoga classes, free food, Friday's off, beer pong, maid service and other things companies are offering. 32 hours a week is nice for some but that doesn't always equate to marketplace monopolization. Then again since Treehouse is competing with others this may not be their goal anyways.
- kvcrawford 12y agoI, for one, immediately checked for Treehouse's open positions. In a world where retention and recruiting are huge challenges for tech, a strong work-life balance policy is very powerful. Too bad they don't have a need for a front-end engineer right now. I would be all over that. Keep up the good work, guys!
- locahost 12y ago+1. I'll keep checking that jobs page as well. In my fifteen years of tech work, the only occasions I had to work overtime were those when somebody screwed up. It was often because somebody didn't say no to requests for: CYA meetings; last-minute scope changes; mandatory "butts in chairs" policies. Thirty-two hours a week doesn't give lousy management enough time to take root. Like kvcrawford, I can't overestimate how appealing that is when it comes time to recruit.
- kaiuhl 12y agoWe don't hire strictly front-end developers, only designers who can write markup, and developers.
- JohnLen 12y agoProductive works that matters. Not the working hours.
- JohnLen 12y agoProductive works that matters. Not the working hours.
- morgante 12y agoWhile I certainly commend them for being able to make this work (we need more innovation in management practices across the board), it does seem like there's a bit of a holier-than-thou trend in this comment thread. As the founding engineer at my current startup, I have tremendous flexibility in setting my own hours but I willingly and intentionally work 60+ hours a week. Not because any manager pushes me to. Not because I even have to. Simply because I genuinely enjoy it. Indeed, work is probably the most enjoyable thing in my life. On a given Friday, I'd rather be building products at work than watching a movie or engaging in some other leisure activity. Some of us don't have wives, children, or friends—we just want to spend our time executing. Would Treehouse be accepting of that? If not, they're just choosing to enforce a different paradigm of work rather than giving their employees true freedom.
- kaiuhl 12y agoNobody is stopped from working longer hours, but the expectation culturally is that you should probably be doing something else instead of working on Sunday.
- morgante 12y agoNot working on Sundays (few professionals do) is pretty different from the 32 hours the article describes. Which is it?
- kaiuhl 12y agoSunday was just an example. Nobody is stopped from working if they're movitated to do so, but we generally discourage each other from working overtime unnecessarily. I personally work 32-hour weeks regularly and still contribute meaningfully. And then, I go backpacking or bike-riding or something that tends to be demanding physically and relaxing mentally—I find it helps me keep a healthy balance. I know there are plenty of people that don't crave that reprieve though, and that's totally okay as well. There's weekends where I'm working on a particularly interesting problem where I'll work through the weekend because I want to. The big difference is the extrinsic pressure is missing. Nobody has to.
- Sir_Substance 12y agoThe stories vary in quality and details, but as far as we can tell the 40 hour week was implemented by Henry Ford in 1926, after careful record keeping and analysis revealed that the ratio of worker output per week to wages paid per week peaked at about 40 hours per week of work. Now, that's fine for factory work, but as far as I know, relatively little effort has been put into testing that theory in knowledge jobs.