7 ms·
I think what you say is true over the long term, but not so much over the short term. Need me to skip breaks and work hours for one day when I'm well rested. I
by nicoburns 6y ago
I think what you say is true over the long term, but not so much over the short term. Need me to skip breaks and work hours for one day when I'm well rested. I definitely can be significantly more productive than usual. Problem is that it's not sustainable.
- Taek 6y agoMost coders I know have had occasional run ins with a rabbit hole where several days of their life got sucked into a single drawn out coding session with little breaks besides food, and had some of the most productive few days of their lives doing that. If you need me to do a three day sprint, I'm going to accomplish the most without any breaks and with very sporadic sleep. (typically when doing a multi day session my sleep happens 30-120 minutes at a time, usually immediately following me hitting a difficult problem that requires intense rumination)
- athenot 6y agoI would much rather code for 3 days non stop and then take a 4 day break doing some outdoors activity. I think the "business hours" schedule is fantastic for meetings to discuss but terrible for creative work. The catch is than in many positions, one needs to blend these 2 modes of operation. Some collaboration, some deep work. Unless there's support throughout the organization, what ends up suffering is the deep work.
- periheli0n 6y agoThe problem is also that meetings and answering emails is much easier than deep work and therefore they are highly attractive procrastination pastimes.
- yonaguska 6y agoUgh. I find them incredibly draining. While if I can actually code for a few hours uninterrupted (this includes self interruption), I find I have so much more energy. Maybe it's the self congratulatory mind manipulation I play on myself when I'm productive. On the other hand, meetings that I have little stake in just exhaust me and derail my ability to focus for the entire day. This may be an ADHD thing though.
- periheli0n 6y agoThat's the trap. I can pull off 16-hour days once in a while. They problem is that once I knew I can do that I tended to factor them into my planning, instead of treating them as the absolute exception that is actually harmful to my health.
- AnimalMuppet 6y ago"Never work overtime longer than one week in a row" - one of Extreme Programming's tenets.
- 0xFACEFEED 6y agoIt took me over 15 years in the industry to realize a couple of things. If you're young and reading this then I hope you at least spend a few minutes thinking deeply about it. 1) Any productivity gained over that one-or-two-day session makes very little difference in the big picture. Even a week. A company/product/feature is never going to live or die on that 30 hours of coding that you managed to squeeze into 48 hours. 99.999% of the time you're doing it to calm people's nerves or make someone (yourself? PM? EM?) look good. 2) My reasons for doing these marathon sessions was a lie. I told myself that I'm doing it because I love the product, love the work, love this, love that. I'm an artisan, I told myself. A professional. Work is my life. Isn't it the same for those Japanese knife maker guys? I'm like those guys. I live this work. The real reason was fear. Fear of not being the best, fear of not being successful, etc. I felt like I didn't have a place among MIT/Stanford grads. So I compensated with brute force. -- It didn't help that I was rewarded with more money, more respect, and more decision making power. I was even rewarded with more knowledge than everyone else -- you learn a lot working 12 hours a day. And if you screw something up you have plenty of time to fix it. Wrote a nasty bug? No problem, ship a fix at 11:30pm and the impact is minimal. People are much less likely to criticize you if you're the person sitting up at 11:30pm shipping to production. Clearly your heart is in the right place, right? The "trick", I found, was to work for people who NEVER EVER demanded more than 7 hours a day from me BUT also appreciated that I'd go well above and beyond expectations. Now that I think about it, it reminds of drug dealing (or the little I know about it from when I was a teen). I feel fortunate that I was able to disassociate my fear of failure from my genuine love for the work. These days I'm able to be very productive and lead a relatively healthy life but it took waaaay too long for me to figure out how.
- curiousllama 6y agoI really like #1. There's a good quote I've been focusing on recently - "people tend to overestimate what they can accomplish in a day, and underestimate what they can accomplish in a year."
- cgrealy 6y agoThis. So much this. At my company, we give out "values awards". People are frequently lauded for working late evenings and weekends. Everytime this happens, I cringe. If people feel they need to do this, it's a sign that projects were under-resourced or the deadlines were too tight. At this point in my career, I am so much more comfortable saying "no" to upper management. "My team does not have capacity for this" "ok, which piece of work do you want us to drop?" "Yep, we can do that... next year"