I'm also gonna need you to go ahead and come in on Sunday, too...

I like weekends.
Don't worry, there's no big insight on "why", I just need to state that in advance.
I don't like working weekends.

I like my job. I like the technology. I'm extremely happy to be able to do what I like with my life.
Y'all are probably like that (blog readers and such, and let's face it - my blog ain't exactly Dilbert or XKCD. More like Maramduke)
I do like learning new stuff and reading technical articles and books in my free time.

</Exposition>

One of my teammates recently encountered a technical issue he could not resolve quickly, on a Thursday afternoon, for a feature he knew was urgent enough to finish. He told me he'll get cracking on it over the weekend and I simply told him not to. I think developers should have some "quite time", both on the "humane" level and also on a professional level - it's good to stop thinking about problems, and then return to them with a fresh slate, with the ability to criticize all the basic assumptions (the phrase "let it sink in" just didn't do it for me).
Nonetheless - the reason I told him not to work on it during the weekend was not because of the professional reasons. Personally, I don't like being told what to do, especially on weekends. I guess other people are like that as well.
So even though he himself has offered to do that task - I'd much rather offering him an easy way out than to let him feel he "had to" do it simply because he "accidentally" volunteered.

And I do appreciate his gesture. I do. I don't have any problems with people honing their technological skills on the weekends ("learn-stuff-make-smart. Booga booga"), reading books, articles and thechniblogs. It's probably very interesting to them. I know I do it because it interests me. But I think that being productive (and not get paid) over the weekend has a certain "odor" to it.

Anyway, I worked this last weekend. The quiet work environment did me good.