When I use Gimp, I code...
Strange experience some years ago. I worked in a project 10km from home and I could get there on a bicycle, about half the distance being on bike lanes in the "Bois de Boulogne", a big park west of Paris. Out of curiosity I got a wearable heartbeat monitor, and the Andoid apps that records the heartbeat and the GPS position. One could clearly see where the steep slopes were.
Usually I would remove the thing during the day, but one day I forgot it and wore it all day. Once back home I downloaded the data. To my surprise there was a 3 hours span in the afternoon where my heartbeat was very slow (somewhat below 50). The next day at work, looking at hard evidence (time stamp on mails, source code and server log files), this was when I was writing code (as an "architect" on that project, I usually didn't write much code, but that part was critical and somewhat easier to code than to explain). So, writing code puts me in some kind of trance (or helps me reach nirvana)
. Why should I stop?
Strange experience some years ago. I worked in a project 10km from home and I could get there on a bicycle, about half the distance being on bike lanes in the "Bois de Boulogne", a big park west of Paris. Out of curiosity I got a wearable heartbeat monitor, and the Andoid apps that records the heartbeat and the GPS position. One could clearly see where the steep slopes were.
Usually I would remove the thing during the day, but one day I forgot it and wore it all day. Once back home I downloaded the data. To my surprise there was a 3 hours span in the afternoon where my heartbeat was very slow (somewhat below 50). The next day at work, looking at hard evidence (time stamp on mails, source code and server log files), this was when I was writing code (as an "architect" on that project, I usually didn't write much code, but that part was critical and somewhat easier to code than to explain). So, writing code puts me in some kind of trance (or helps me reach nirvana)
. Why should I stop?