Earlier quoted context omitted.
I'm not suggesting someone spend all of their time writing code outside of work, I certainly don't, so please don't label what I'm saying as such, or as "bullshit". Yes employers pull that crap, and want you to sell your soul, that's not what I'm suggesting. I don't think programming is something you become good at simply by doing your 9-5. I've worked with a lot of 9-5'ers and they're rarely the best or most rewarde…
I don't disagree with most of what you say, however: If you have a (code) problem at the end of the day it's often best to just stop - maybe even finish early. When you sit down in the morning more often than not it'll seem much easier to fix, your subconscious will have been working on it overnight. That's better than sitting there for another hour or two in the evening getting increasingly tired and ineffective, mi…
This is the part about not taking your work home. I'm often pre-occupied with problems I haven't solved, I find for me, taking the time to solve them, or to be sure that I can't solve it now helps with that.
I'm not disagreeing with you, some problems need to be left for another day, and I've said that already.
What I'm trying to say is that I think we're both right in a way, and that finding balance is what we need.