Watching TV?? That's the most horrible advice I've seen in a long time ...
I wouldn't choose it either, but it depends what your outside options are. At least it gets you thinking about people and processing verbally.
Reversing the effects of long programming sessions
51–60 of 144 posts
Re: Reversing the effects of long programming sessions
#52I think basically anything else will do. I tend to do quite a bit of diy in my spare time. But I have to say. After a long programming session I turn into the most egotistical angry creature I have ever known. Thankfully the productivity of such a session is usually so big people still go to their knees to thank me. And I happen to be a real sucker for compliments so once in a while when it's really necessary I still do them.
Re: Reversing the effects of long programming sessions
#53When I played poker for a living I would sit for like 12-16hrs at a table glued in thinking in fractions and ratios. I couldn't even count the chips when I went to the cage after, it wasn't in ratios. I would meet friends at a bar/club and couldn't talk to anyone for at least an hour.
They should add:
- Weed - Drinking - Porn
There is no way I could play video games.
Re: Reversing the effects of long programming sessions
#54'Take a nap' ought to be on the list. A) Naps are awesome. B) Putting down that mental model of functions, open files, and unsolved problems for a while often results in sharper thinking. Not gonna lie though - most of my unwinding consists of refreshing HN, daytrading Bitcoin or making another cup of coffee. But ideally I'm napping.
I can't sleep (unless I'm extremely deprived, at which point I'm really just passing out) until after I've done the unwind things mentioned in the article and have been away from work for ~3 hours. It doesn't matter when I stop working, I cannot sleep until 3 hours has passed. I've tried, I lay in bed for 3 hours minus commute time.
Re: Reversing the effects of long programming sessions
#55We 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'm finding that 'flow' is a significant contributor to NIH Syndrome.
You can't flow while integrating a third party library anywhere near as easily as you can flow by rewriting half of it (badly) from scratch.
Flow is a rush. Anything that is a rush can be indulged in to the point of self- (or other-) harm.
Re: Reversing the effects of long programming sessions
#56Earlier quoted context omitted.
When I work 13 hours 3 days in a row my employer still expects me to show up for the remaining 2 days of the week. If I had a fixed 40 hours week I would be done and could recover these 2 days. I also don't get more money for working more.
Sounds like a problem with your employer. None of mine have ever had a problem with me taking off early to make up for days I've worked longer hours. Have you talked to them about it?
I have talked about this. From my experience it's very common in tech to let people work longer without compensation in time or money.
Re: Reversing the effects of long programming sessions
#57We 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…
> blue light that damages your vision Can anyone explain to me how looking at a computer screen is not several times less harmful than spending time outside from a lifetime-blue-light-exposure perspective? The sky is blue and natural light has a blue component in probably about the same proportion as white light from a screen. Maybe I'm wrong — and I'd like to find out if I am — but this whole blue light scare really…
Regardless, blinking less often and focusing purely on a 2d image will degrade your vision
Re: Reversing the effects of long programming sessions
#58Earlier quoted context omitted.
I can't listen to anything with words I understand. Podcasts would be ridiculous.
Right; I'm unable to even listen to music while in deep flow, because I have a composition/conducting background, and ANY kind of music triggers analysis that is a distraction. I just listen to white noise.
If you’re a composer/conductor then you’ve probably already tried this, but for me two types of music work well (as I’m a similarly analytical musician):
- Minimalism, specifically Steve Reich’s Music for 18 Musicians suite
- Atmospheric, specifically ‘Skyrim Atmospheres’ by Jeremy Soule
Both are so versatile: minimalism for journeys and coding; atmospheric for ‘creative’ periods, walking and sleeping. I do somewhat envy your ability to listen to white noise as it is infinitely replicable, but fear it a little distracting in of itself!
Re: Reversing the effects of long programming sessions
#59Earlier quoted context omitted.
All true, but neither should we deny ourselves a long session of "flow" if it makes us happy.
I'm finding that 'flow' is a significant contributor to NIH Syndrome. You can't flow while integrating a third party library anywhere near as easily as you can flow by rewriting half of it (badly) from scratch. Flow is a rush. Anything that is a rush can be indulged in to the point of self- (or other-) harm.
> You can't flow while integrating a third party library anywhere near as easily as you can flow by rewriting half of it (badly) from scratch.
That is not so clear cut, it depends on the library. If the documentation sucks or the library is a mess, rewriting it may both induce flow and be a win for the team.
Re: Reversing the effects of long programming sessions
#60I'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.
Agreed, and since 99% of programming doesn't even involve writing code, it might be healthier to "program" away from the screen, while going on a walk for example.