Earlier quoted context omitted.
I think the issue here is when people take that viewpoint as a career. I code for a career. I also code for a hobby. I code for fun. They're different. You can eat. sleep. code. repeat. without it being eat. sleep. work. repeat. And you can mean it lightheartedly/halfheartedly as well. "Eat, sleep, game, repeat." can be the same thing. Obviously taking it literally is unhealthy, but I don't think anyone is proposing…
I don't know if you're young, obviously, but this is a young, or at least unattached, person's point of view. I taught myself to program in the 80's when I was in my early 20's. In my later 20's and through my early 30's I did it for fun and profit, often working on a project 14 or more hours a day. By the time I got into my early 40's I had a wife, three young children, a house, a couple of pets, etc. to go along wi…
I found this passage from the works of Thich Nhat Hanh very helpful to deal with that, YMMV.
“Then Allen said, “I’ve discovered a way to have a lot more time. In the past, I used to look at my time as if it were divided into several parts. One part I reserved for Joey, another part was for Sue, another part to help with Ana, another part for household work. The time left over I considered my own. I could read, write, do research, go for walks. But now I try not to divide time into parts anymore. I consider my time with Joey and Sue as my own time. When I help Joey with his homework, I try to find ways of seeing his time as my own time. I go through his lesson with him, sharing his presence and finding ways to be interested in what we do during that time. The time for him becomes my own time. The same with Sue. The remarkable thing is that now I have unlimited time for myself!”