3 ms·

For me, some days it would be awesome, on others it would be stressful as shit. What I would prefer is to work as long as I need to and when I come to a logica

For me, some days it would be awesome, on others it would be stressful as shit. What I would prefer is to work as long as I need to and when I come to a logical breaking point, I go home. Some days that may be 4 hours, other days that may be 12. Some things I can't easily break down into chunks that easily fit into 8 hours and not have me lose my place by going to sleep. Some days I get into a flow and I don't even realize I'm hungry until it's dark again and I suddenly realize everyone's gone to bed and left me on my own. Other days I struggle to figure out what I'm doing and the more I fight it, the harder the struggle becomes. It's not because of a lack of discipline or lack of want to work, it's just that I struggle to connect dots that when I'm on form just connect themselves. On days when I'm on form, I'm unstoppable, a machine that just churns out working, tested, simple, elegant solutions to problems. When I'm not on form, I can't figure out how chew gum without gagging. This seems to hinge on how much sleep I've had, which directly impedes the amount of time I have in a day... finding the balance between enough sleep and enough time to get work done to a high degree of quality is a constant struggle So I don't think changing the length of the work day for me even enters in to my psyche. It's always either far too long or nowhere near long enough... it would be the same if the work day was 2 hours long or 22 hours long. That's what it's like for me, I can't speak for everyone else.

morinted 10y ago
This rings quite true with my experience. There are days where I leave early because I'm not being productive due to…you know, just the brain being weird.
Sharlin 10y ago
It doesn't really make much sense to talk about the length of a work day except on average. "Six-hour work day" should just be interpreted to mean "120 hour work month" or similar.
- gbhn 10y ago
  I think many of us on this site have jobs where presence and productivity are pretty elastic. Many workers have jobs where human presence is a key part of the job function. Being a cashier, or a nurse, or driving -- it isn't as though these things happen unless you are physically there. The quantum of human presence is "one human" :-) so even if there are no customers, the driving is boring, or the patients are asleep, it still requires you to be there on the job.
  - Sharlin 10y ago
    Yes, sure. I was unclear but meant in "our" field (IT).
pweissbrod 10y ago
If I was able to work with nothing but people as honest and driven as yourself then I'd have an extremely efficient company with ideal schedules.
- balabaster 10y ago
  Alas, there's only one me, so your company probably isn't :P I kid around. Of course, we're all human and we're never all on form on the same day and shit happens and unexpected problems need to be solved right now and the only guy on form has no idea of the problem domain and the only guy who does understand it is 20 hours into a 22 hour day and has bloodshot eyes. This is life, reality. Sadly it doesn't understand ideal. It's all about compromise for the greatest good we can achieve today to meet our goals tomorrow. C'est la vie.
awjr 10y ago
> What I would prefer is to work as long as I need to and when I come to a logical breaking point, I go home. The only issue with this approach is that what you perceive a logical breaking point and what your boss perceives as a logical breaking point will be very different. "Before you go, can you just fix ..." Even 8 hour days can result in this behaviour becoming 10+ hour days.
- balabaster 10y ago
  That's true... I think we need to be more congizant of this - if I fix this one thing now, is it going to significantly improve ROI over if I do it tomorrow when I'm well rested?
xherberta 10y ago
I know someone who asked to go from salaried to hourly for this reason - he didn't want to sit there and ride the clock if he wasn't actually able to be productive during that time. The (engineering) company operated based on billable hours, so they loved it, initially. Eventually, though, you stop fitting in to the organization when you're a part-timer.
maxxxxx 10y ago
That's what I did as freelancer. I often did my 40 hours work week in 3 days. And I think I did better work that way. In my corporate job I often don't have an inspiration at 9 am so I pretty much sit around and pretend to be busy. It would be much better to take off that time. And then you have that moment where everything makes sense and can crank it out in 18 hours. Unfortunately programming is treated like assembly line work where every hour (and every worker) is equal. I don't think this reflects reality well.
- RUG3Y 10y ago
  This is how I work as well. Things stew around until everything clicks and then I crank out 3 days work in 3 hours.
  - st3v3r 10y ago
    If that's the case, then it really wasn't 3 days of work.
    - maxxxxx 10y ago
      It's the same output as if you were sitting in an office 8 hours a day for 3 days.
- reloop 10y ago
  I used to do this early in my career too, until I realized how counterproductive it was. I've found that it isn't "coding marathons" themselves that are good, but being motivated, undisturbed, structured etc. Few people are that everyday, so we have to work on it. Nowadays instead of coding full out until I go home and crash on the couch I try to spend the last hour of the work day documenting what I've done, what need to be done tomorrow and even what I'm doing this evening. That way I've probably had some decent time off, I know what to do the next day and can more easily get started. Even if I'm not motivated I can do something simple for a couple of hours, at which point I usually get motivated again. Coding marathons feels good when you do them, but they also builds up debt. Both in the structure of the project and in motivation. It's quite natural that it's hard to get started if you don't have an obvious starting point and you anticipate that you have to do a full 8 to 10 hours and be completely spent at the end.

morinted 10y ago

This rings quite true with my experience. There are days where I leave early because I'm not being productive due to…you know, just the brain being weird.

Sharlin 10y ago

It doesn't really make much sense to talk about the length of a work day except on average. "Six-hour work day" should just be interpreted to mean "120 hour work month" or similar.

gbhn 10y ago
I think many of us on this site have jobs where presence and productivity are pretty elastic. Many workers have jobs where human presence is a key part of the job function. Being a cashier, or a nurse, or driving -- it isn't as though these things happen unless you are physically there. The quantum of human presence is "one human" :-) so even if there are no customers, the driving is boring, or the patients are asleep, it still requires you to be there on the job.
- Sharlin 10y ago
  Yes, sure. I was unclear but meant in "our" field (IT).

pweissbrod 10y ago

If I was able to work with nothing but people as honest and driven as yourself then I'd have an extremely efficient company with ideal schedules.

balabaster 10y ago
Alas, there's only one me, so your company probably isn't :P I kid around. Of course, we're all human and we're never all on form on the same day and shit happens and unexpected problems need to be solved right now and the only guy on form has no idea of the problem domain and the only guy who does understand it is 20 hours into a 22 hour day and has bloodshot eyes. This is life, reality. Sadly it doesn't understand ideal. It's all about compromise for the greatest good we can achieve today to meet our goals tomorrow. C'est la vie.

awjr 10y ago

> What I would prefer is to work as long as I need to and when I come to a logical breaking point, I go home. The only issue with this approach is that what you perceive a logical breaking point and what your boss perceives as a logical breaking point will be very different. "Before you go, can you just fix ..." Even 8 hour days can result in this behaviour becoming 10+ hour days.

balabaster 10y ago
That's true... I think we need to be more congizant of this - if I fix this one thing now, is it going to significantly improve ROI over if I do it tomorrow when I'm well rested?

xherberta 10y ago

I know someone who asked to go from salaried to hourly for this reason - he didn't want to sit there and ride the clock if he wasn't actually able to be productive during that time. The (engineering) company operated based on billable hours, so they loved it, initially. Eventually, though, you stop fitting in to the organization when you're a part-timer.

maxxxxx 10y ago

That's what I did as freelancer. I often did my 40 hours work week in 3 days. And I think I did better work that way. In my corporate job I often don't have an inspiration at 9 am so I pretty much sit around and pretend to be busy. It would be much better to take off that time. And then you have that moment where everything makes sense and can crank it out in 18 hours. Unfortunately programming is treated like assembly line work where every hour (and every worker) is equal. I don't think this reflects reality well.

RUG3Y 10y ago
This is how I work as well. Things stew around until everything clicks and then I crank out 3 days work in 3 hours.
- st3v3r 10y ago
  If that's the case, then it really wasn't 3 days of work.
  - maxxxxx 10y ago
    It's the same output as if you were sitting in an office 8 hours a day for 3 days.
reloop 10y ago
I used to do this early in my career too, until I realized how counterproductive it was. I've found that it isn't "coding marathons" themselves that are good, but being motivated, undisturbed, structured etc. Few people are that everyday, so we have to work on it. Nowadays instead of coding full out until I go home and crash on the couch I try to spend the last hour of the work day documenting what I've done, what need to be done tomorrow and even what I'm doing this evening. That way I've probably had some decent time off, I know what to do the next day and can more easily get started. Even if I'm not motivated I can do something simple for a couple of hours, at which point I usually get motivated again. Coding marathons feels good when you do them, but they also builds up debt. Both in the structure of the project and in motivation. It's quite natural that it's hard to get started if you don't have an obvious starting point and you anticipate that you have to do a full 8 to 10 hours and be completely spent at the end.