When I used to work outside of my home this meant playing table tennis or fußball as a clearing ones mind method. Or going for a walk outside of the workplace.
The gung-ho brute forcing of a coding method is a dangerous path to traverse. I'm more for the cyclical clear ones mind, allow the design/ideas/concepts to brew. Commit to code the portion at hand then cool down and repeat the cycle.
Honestly, my best clarity comes at 2am, the shower and/or commutes >20 minutes.
Eric codedevl.blogspot.com
I spend about 35 hours a week at the office or customers premises. I spend 80 to 100 hours a week doing work-related stuff. I may pretend that I'm working even while I'm running in the woods, every morning, because while I run I'm probably rummaging about a couple of work related problems, even if it's on the back burner.
What's work? Frankly, I don't know anymore.
I'm employed full-time, but I'll be the first to admit that for not all of that I'm working. Outside of that I have projects I'm working on (which I'd be inclined to count as work) and a small business (which is definitely work though I treat that more as pleasure).
I guess if it's vague enough to just be anything not personal or sleeping then > 60 hours... but if it's constrained to that for which I am employed/get paid, then it's variable.