Chris Sells has been writing on working at home, and
Scott Hanselman has as well.
As for myself, my employer frowns on working at home, although I am on a laptop, and we do have a VPN. Several times I have gotten permission to work from home simply so I can focus on one project at a time and actually accomplish things.
My normal course of action is to keep accepting small tasks that 'should be done easily' and then have them pile up as the daily fires appear and consume my time.
Ultimately, my to do list threatens to suck my computer into the void due to its massive gravitational weight and I have to blow everyone off and get the plate clean again.
I'm not sure if working full time from home would work from me, I certainly doubt my employer would buy into it. But currently, I'm sitting at the office trying to play the same game of catch-up. It's 10pm and I'd rather be home to do this work.
Earlier Jeff Brown posted some
comments on some new features of MbUnit v3, which I responded to by how to answer the NUnit critics concerning isolation of test fixtures.
Jeff
responded with what I think is a pretty good answer. I'll have to think it through for a bit.
I believe that my original question was not so much a question of the validity of the approaches, but that after reading the book, I found that I had not considered the original issue of isolation via new test fixture classes.
I started with NUnit as my first experience and not JUnit, so the set and tear down mechanisms were just 'what was' rather than what should be.
As I've said in my other posts, I am often constrained by decisions made from outside my organization and the choice of unit testing framework is no different so having the best arsenal of responses to the unavoidable battles for these types of choices is a good thing.