[steveklabnik]

I've been developing a concept called "irresponsible coding," which is basically the idea that you need 'good engineering' time as well as some form of 'irresponsible, exploratory coding.' I've given a few talks on it: http://www.youtube.com/watch?v=XlyQOLRiEPs

I think that we've often lost a lot of the wonder and whimsy in software. Code is like magic! But you don't get that when BDDing a new feature so you can check it off in Pivotal.

I agree that not coding every single day is a really fantastic idea as well.

[moultano]

I personally think that's the best part about 20% time. You can do things where it's OK for them to not work. This means you can try things you don't know how to do, and bring them in to your main projects once you are already comfortable with them.

[sanderjd]

I like the idea of a "day off" being either a real day off, or just a day where you code irresponsibly, whichever will be more rejuvenating. Thanks for the terminology!