That is what the individual is going to end up doing if they encounter the guy who thinks software is built on an assembly line, but is not ideal. The reviewer might get "the itch" before Monday. It would be a waste to see him fall into burnout because he had to artificially wait because you had to pretend to wait.
You don't burn out because you weren't working. That's not a thing.
I am concerned about how you describe coding as an addiction. That sounds like something worth bringing up with a therapist & investigating the root cause of. It can be literally dangerous to identify that much with only our work, especially in this economy.
But if you don't want to do that, if you have some rare code-or-die health condition, just contribute to some Apache project instead. The entire internet is build on projects people wrote that their companies didn't pay them to write. We don't have to give our whole creative selves to our employers.
If you never had to work then you would never burn out, sure. But returning back from la-la land, most people are going to have to work. As was stated before, burnout ensues when one forces themselves to work when they are not in the right frame of mind to do so. If you code by the rule of the calendar, that is what is going to put you at risk of burnout. If you code when your mind says "Let's go" and stop when your mind says "That's enough", chances are you'll never experience it.
Denying a "let's go" moment on Saturday, to fight with a "that's enough" moment on Monday because the calendar says you cannot work on Saturday but must work on Monday is a good way to end up with burnout. But why fight it? Why not just work on Saturday and take Monday off? It is not going to make any difference in the end. The deliverable will be there at the anticipated time either way.
> I am concerned about how you describe coding as an addiction.
What is this addiction you are referring to? I can find no mention of it anywhere in this thread before this.
