I found the best way for me to unwind is exercise. Table tennis or especially boxing works really well too. Nothing makes you switch mode faster than getting hit in the face :)
Reversing the effects of long programming sessions
21–30 of 144 posts
Re: Reversing the effects of long programming sessions
#22We need to restrict the amount of hours we spend in front of computers per day and take weekends completely off. There are so many downsides: blue light that damages your vision, lack of exercise, depression and other disorders, missing out on social life, etc. There is a direct relation between productivity and having a life put together. Not taking care of ourselves (programmers) could have lead to disaster: mental…
Pretty much the same with deadlines. If the workload is reasonable it'll get done in good time. Might even to be my own schedule and not a 9-5 but it will for sure get done. I will even avoid the flow unless I feel particularly meditative. There's nothing good about vanishing down a rabbit hole for several hours and prioritising the rabbit hole above your own health.
Sometimes the deadlines are unavoidable, but when a manager creates a deadline based on estimated development time I have decided to push back.
Also I now refuse to do single estimates, but instead provide more of a histogram that shows how probable I think various estimates are (basically a minor risk assessment).
Re: Reversing the effects of long programming sessions
#23We need to restrict the amount of hours we spend in front of computers per day and take weekends completely off. There are so many downsides: blue light that damages your vision, lack of exercise, depression and other disorders, missing out on social life, etc. There is a direct relation between productivity and having a life put together. Not taking care of ourselves (programmers) could have lead to disaster: mental…
All true, but neither should we deny ourselves a long session of "flow" if it makes us happy.
That's why it would be good to get paid by hour. When I was freelancer when things flowed I sometimes worked 24+ hours straight through or had several 16 hours days. But then I had other days when I got nothing done and took off. In a salaried position the company takes the long "flow" session for free but still expects you to be there the next day.
Re: Reversing the effects of long programming sessions
#24"Personally I cannot listen to technical podcasts while I develop software"
What? I've never known anybody that could do that! Anyone that can do that meaningfully must be some kind of savant.
Re: Reversing the effects of long programming sessions
#25I've found that the most important thing is not engaging in marathon sessions, full stop. My code is better, I'm healthier, and I get more done per working minute. Take a break every hour or so, minimum ten minutes, and step away. Make coffee, ponder the infinite, pet your cat, listen to some Chicago or Slayer, whatever suits your preferences.
> Chicago or Slayer
Really covering a wide gamut here!
Re: Reversing the effects of long programming sessions
#26Here are a few other suggestions:- - Playing video games - Cooking - Watching TV - Listening to music - Talking to non-technical friends - Closing my eyes and slow your breathing - Exercise I can see all but video games and watching TV, where again you sit in front of a screen. Doesn’t help me. Instead, I’d add hiking in the hills, forest, mountains, being outside in nature in general. Nothing is more re-energizing f…
Video games work for me in getting my mind to let go of the problems it's pondering about. Sometimes it's like subconscious I'm always working on some problem. Videogames at least let me forget/drown-out certain 'work'-like problems and allow me to reward myself instead with 'fun' problems. Walking often just leaves my senses empty and causes my mind to focus on the work problems again. Maybe a hike would be different as you are more exploring something new to keep your mind occupied.
Re: Reversing the effects of long programming sessions
#27Watching TV??
That's the most horrible advice I've seen in a long time ...
Re: Reversing the effects of long programming sessions
#28In this last project I was in, which was a bit of a death march - we (Team) ALL got to the point of incurring bizarre sleep disturbances and other cognitive/emotional disturbances: It would take 3-4 hours once home at our set stop time to "shut off" our brains from thinking about what we were working on - and switch over to "being home" mode and interacting with spouses etc. without being irritable. We also all had d…
I have "programming dreams" every night.
Probably isn't healthy, but I program all day at work. Go home and spend a few hours with family, then program an additional few hours every night. Sometimes I fall into the rabbit hole and emerge at 2-3 am after finally finishing what I started. Go to bed, and rinse and repeat the next day.
My brain just won't shut off at this point, but I enjoy absolutely everything about what I do.
Re: Reversing the effects of long programming sessions
#29We need to restrict the amount of hours we spend in front of computers per day and take weekends completely off. There are so many downsides: blue light that damages your vision, lack of exercise, depression and other disorders, missing out on social life, etc. There is a direct relation between productivity and having a life put together. Not taking care of ourselves (programmers) could have lead to disaster: mental…
Pretty much the same with deadlines. If the workload is reasonable it'll get done in good time. Might even to be my own schedule and not a 9-5 but it will for sure get done. I will even avoid the flow unless I feel particularly meditative. There's nothing good about vanishing down a rabbit hole for several hours and prioritising the rabbit hole above your own health.
Is there a formalized definition of this "rabbit hole" people have been abusing ever since The Matrix was in theatres? I feel like it was originally a metaphor but it's being used more and more literally to where I hear it almost daily.
Re: Reversing the effects of long programming sessions
#30We need to restrict the amount of hours we spend in front of computers per day and take weekends completely off. There are so many downsides: blue light that damages your vision, lack of exercise, depression and other disorders, missing out on social life, etc. There is a direct relation between productivity and having a life put together. Not taking care of ourselves (programmers) could have lead to disaster: mental…
All true, but neither should we deny ourselves a long session of "flow" if it makes us happy.
I love flow, it makes me feel great. But it doesn't make me happy - just grumpy when people interrupt me, and impatient when I'm in social occasions when people are making small talk.