> Working slowly after hours with no promise of getting much if anything concrete done is a deep joy for some of us. I sometimes need to play with my work to kn

> Working slowly after hours with no promise of getting much if anything concrete done is a deep joy for some of us. I sometimes need to play with my work to know what I'm doing tomorrow. It could be argued that code exploration at the pace you need should be part of your regular working hours, if that is what is needed to do your job efficiently. In the extreme, not allowing your employees to do so is failed management. Of course, the knowledge and efficiency you gain by doing so is not measurable by any quantifiable metric, so it's easy to see how it will be conveniently discarded as unnecessarily. Even better, by having you convinced that it is something you should do in your own free time, they can reap the benefits without the costs. Full profit.